Skip to content

ci(qemu): use IMAGE_CLASSES for testimage, not INHERIT#7

Merged
EmbeddedAndroid merged 1 commit into
mainfrom
fix-testimage-inherit
May 14, 2026
Merged

ci(qemu): use IMAGE_CLASSES for testimage, not INHERIT#7
EmbeddedAndroid merged 1 commit into
mainfrom
fix-testimage-inherit

Conversation

@EmbeddedAndroid

Copy link
Copy Markdown
Owner

First dispatch of the qemu-runtime workflow failed at the Configure build step:

ParseError in configuration INHERITs: Could not inherit file classes/testimage.bbclass

testimage isn't meant to be inherited globally via INHERIT. The Yocto pattern is IMAGE_CLASSES += "testimage" so it only attaches to image recipes (and bitbake finds it under classes-recipe/ in scarthgap where the old classes/ was split).

Trivial one-line fix to local.conf in qemu-runtime.yml.

INHERIT += "testimage" failed at parse time with 'Could not
inherit file classes/testimage.bbclass'; testimage isn't meant to
be inherited globally. The canonical Yocto pattern is
IMAGE_CLASSES += "testimage" so it only inherits on image
recipes (and bitbake finds it under classes-recipe/ in scarthgap
where classes/ was split).
@EmbeddedAndroid EmbeddedAndroid merged commit c9f7901 into main May 14, 2026
22 checks passed
@EmbeddedAndroid EmbeddedAndroid deleted the fix-testimage-inherit branch May 14, 2026 22:43
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