Skip to content

Conversation

a-wai
Copy link
Contributor

@a-wai a-wai commented Oct 8, 2025

The base_name attribute is now used (when present) as the LAVA device
type, similarly to its usage in the legacy KernelCI. However, this
breaks job submission for ChromeBooks as we used this attribute in a
different way and relied on jobs to be submitted with the platform name
being used as device type.

In order to fix this, drop base_name entirely from all ChromeBook
platform definitions (this is an optional attribute anyway) so we
default back to using the platform name as the LAVA device type. Also
use a new params[short_name] attribute as a replacement for our
previous use of base_name here.

This PR also includes a tiny improvement to the qemu-arm platform definition.

a-wai added 2 commits October 8, 2025 11:51
The `base_name` attribute is now used (when present) as the LAVA device
type, similarly to its usage in the legacy KernelCI. However, this
breaks job submission for ChromeBooks as we used this attribute in a
different way and relied on jobs to be submitted with the platform name
being used as device type.

In order to fix this, drop `base_name` entirely from all ChromeBook
platform definitions (this is an optional attribute anyway) so we
default back to using the platform name as the LAVA device type. Also
use a new `params[short_name]` attribute as a replacement for our
previous use of `base_name` here.

Signed-off-by: Arnaud Ferraris <[email protected]>
No need to redefine `base_name` for `qemu-arm` as this attribute is
already part of the `qemu-device` anchor.

Signed-off-by: Arnaud Ferraris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant