| Summary: | u-boot build failure in Sumo | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> | ||||
| Component: | deployment | Assignee: | Armin Kuster <akuster> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | JPEWhacker, marek.vasut, richard.purdie, xypron.glpk | ||||
| Version: | 2.5 | ||||||
| Target Milestone: | 2.5.1 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| URL: | https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/957/steps/BuildImages_1/logs/stdio | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Ross Burton
2018-04-20 14:52:57 UTC
Others have reported this: http://u-boot.10912.n7.nabble.com/Parallel-make-issue-with-helloworld-efi-td311393.html#a330372 Created attachment 4346 [details]
Wind River u-boot bug log
This is failure mode is quite rare. We build different configurations of Yocto around >500 times a day. I've only seen this once this year so you'd have to add some delays to the build to force it to happen. We could take proposed patches to soak them in our build cluster.
The specific race condition for helloword.efi was fixed with https://lists.denx.de/pipermail/u-boot/2018-May/329738.html As a whole the U-Boot build system is not safe to use for parallel builds. What u-boot release has that shipped in? Patch https://lists.denx.de/pipermail/u-boot/2018-May/329738.html is contained in U-Boot v2018.07. This was fixed in upstream u-boot (2018.07), but still affect sumo since it is consuming 2018.01 I have pushed the patch to the mailing list for the backport in sumo proper http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=sumo&id=e4f158a4610a77886b3dcd641fbfc5959ed58f40 closing |