Created attachment 1035 [details] autobuilder log snapshot qemuppc nighlty build fails when aplying patches for linux-yocto_3.4. See attached log or link [1] for error details. [1] http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/771/steps/shell_29/logs/stdio
Please include the relevant part of the log in the bug and not just paste the link from failure email into a bug report.
I think the bug has the relevant part of the log already attached, does it not?
ERROR: Function failed: do_patch (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/temp/log.do_patch.18404 for further information) ERROR: Logfile of failure stored in: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/temp/log.do_patch.18404 Log data follows: | DEBUG: Executing shell function do_patch | Deleted branch meta-temp (was 580ac9c). | find: `meta/cfg/scratch': No such file or directory | ERROR. Could not locate meta series for qemuppc | NOTE: feature features/kprobes/kprobes.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/features/systemtap) | NOTE: feature features/kprobes/kprobes.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/features/systemtap) | NOTE: feature features/kprobes/kprobes.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/features/systemtap) | NOTE: feature ipsec.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/cfg/net) | NOTE: feature ipsec.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/cfg/net) | NOTE: feature ipsec.scc is included multiple times (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/linux/meta/cfg/kernel-cache/cfg/net) | ERROR. Could not apply patches for qemuppc. | Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto) | ERROR: Function failed: do_patch (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/linux-yocto/3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3/temp/log.do_patch.18404 for further information) NOTE: recipe linux-yocto-3.4.26+gitAUTOINC+c0b3904d60830e24b3930b0fa606a48b2758d979_d771422df10af41ee61598f4aa06e3c3a018c323-r4.3: task do_patch: Failed ERROR: Task 535 (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/meta/recipes-kernel/linux/linux-yocto_3.4.bb, do_patch) failed with exit code '1'
Laurentiu, yes the log was attached, apologies. In the future, unless the log is crazy long, please include in the bug report itself. The actual failure should be evident in the text of the report.
Bruce can you have a look please?
I can look, but there's been *zero* changes to the kernel in over a week. When's the last good build ? Also note: I have no cycles to look at this until tomorrow.
While waiting for confirmation/info about the last known good build. I'll have a look at the autobuilder broken build. How long will it be around ?
I've built this on 5 different machines out of master. All have worked. I'm parking this for a moment, when it shows up again, I can inspect the breakage on the builder.
Can't reproduce so close for now.