Bug 1772

Summary: bzImage missing for atom-pc
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Beth Flanagan <elizabeth.flanagan>
Component: meta-yoctoAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: poky.bs.watcher, poky.watcher
Version: 1.0   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Beth Flanagan 2011-11-17 16:35:10 UTC
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.
Comment 1 Richard Purdie 2011-11-17 16:42:10 UTC
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,
Comment 2 Richard Purdie 2011-11-17 16:52:11 UTC
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.
Comment 3 Richard Purdie 2011-11-24 05:51:44 UTC
This was a sstate related bug and has been resolved in master with the various sstate fixes.