From the autobuilder: http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/230/steps/shell_30/logs/stdio ERROR: Function 'build_boot_bin' failed (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/atom_pc-poky-linux/core-image-minimal-1.0-r0/temp/log.do_bootimg.22376 for further information) ERROR: Logfile of failure stored in: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/atom_pc-poky-linux/core-image-minimal-1.0-r0/temp/log.do_bootimg.22376 Log data follows: | ERROR: Function 'build_boot_bin' failed (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/atom_pc-poky-linux/core-image-minimal-1.0-r0/temp/log.do_bootimg.22376 for further information) | install: cannot stat `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/atom-pc/kernel/bzImage': No such file or directory Rebuilding with a clean sstate to see if this is reproducible.
I'm guessing this file is being poked into the sysroot without sstate knowing what is happening. The solution would be to stage the file in the same manner as the other kernel sysroot files so that sstate does get to know about it and bring it back when needed,
I'm wrong, we need to teach something about the extra tasks: do_kernel_checkout do_validate_branches do_kernel_configme since these are somehow confusing the sstate install. I confirmed the bzImage is contained in the populate_sysroot sstate package.
This was a sstate related bug and has been resolved in master with the various sstate fixes.