| Summary: | Fragment usability issues | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Richard Purdie <richard.purdie> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | ccasciato, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 0.0.0 | ||
| Target Milestone: | 6.2 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2025-01-07 12:24:27 UTC
It turns out I was missing the layer prefix so the fragment wasn't configured. What puzzles me is why some builds with this configured were not erroring in some cases, e.g.: https://valkyrie.yoctoproject.org/#/builders/10/builds/763/steps/10/logs/stdio has: OE_FRAGMENTS += 'yocto-autobuilder/autobuilder' yet the build is proceeding? I'd note the config tool also errored with the description missing once I fixed the short logs. The config tool doesn't like adding require conf/multilib.conf to a fragment. The conf/multilib.conf issue also appears in an oe-selftest failure of bblayers.BitbakeConfigBuild.test_enable_disable_fragments https://valkyrie.yoctoproject.org/#/builders/76/builds/727/steps/15/logs/stdio I sent a patch for the multilib issue. There seem to be other issues here, but I am not sure how to reproduce and observe them. Can I trigger something on the autobuilder against some branches you made, or maybe there are steps I can take locally? conf/multilib issue is fixed. Richard plans to add more info when he is in a more coherent state. ;-) |