Created attachment 4309 [details] Patch to add 2 qemu arm machines (that are slightly different) and INITRAMFS_IMAGE to core-image-sato Background: We have qemuarm1 & qemuarm2 MACHINE entries which include arm9tdmi and arm920t .inc files. Additionally patch core-image-sato with line IMAGE_INITRAMFS = "core-image-base" Steps to Reproduce: Have a build machine with high num of CPU cores 39 or more 1) Apply Patch to core-image-sato 2) source oe-init-build-env 2a) Change local.conf to use PACKAGE_CLASSES = "package_deb" 3) export MACHINE=qemuarm1 4) bitbake core-image-sato 5) export MACHINE=qemuarm2 6) bitbake core-image-sato Actual Results: Recipe core-image-base fails with [log_check] E: Could not open file ./<debian_file>.deb - open (2: No such file or directory) This fails the build of core-image-sato. Also, on more look of log.do_rootfs of core-image-base, we can see multiple warnings of W: Unable to stat ./<debian_file>.deb In both cases, <debian_file> references any debian file because there is no control on when this race happens. Expected Results: Build finishes cleanly without any warnings or errors. Build Date & Platform: Yocto/Bitbake version 2.2 Additional information: This repros only when build is run on highly parallel machines like CPU cores (with HT) = 39
>> IMAGE_INITRAMFS = "core-image-base" It should be INITRAMFS_IMAGE = "core-image-base" Updating patch, please use repro_bug.patch
Created attachment 4311 [details] repro_bug.patch
Created attachment 4312 [details] repro_bug.patch
I wont be able to reproduce this as don't have access to anything with more than 4 cores.
at this time I do not intend on fixing this issue
closing