opensuse423-ty-1 master-next ERROR: core-image-minimal-1.0-r0 do_image_cpio: Function failed: do_image_cpio (log file is located at /home/pokybuild/yocto-worker/oe-selftest-opensuse/build/build-st-9429/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_cpio.42412) ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/oe-selftest-opensuse/build/build-st-9429/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_cpio.42412 Log data follows: | DEBUG: Executing python function set_image_size | DEBUG: 12173.200000 = 9364 * 1.300000 | DEBUG: 12173.200000 = max(12173.200000, 8192)[12173.200000] + 1 | DEBUG: 12174.000000 = int(12173.200000) | DEBUG: 12174 = aligned(12174) | DEBUG: returning 12174 | DEBUG: Python function set_image_size finished | DEBUG: Executing shell function do_image_cpio | 16023 blocks | /home/pokybuild/yocto-worker/oe-selftest-opensuse/build/build-st-9429/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/run.do_image_cpio.42412: line 112: 42718 Done echo ./init | 42719 Segmentation fault (core dumped) | cpio -oA -H newc -F /home/pokybuild/yocto-worker/oe-selftest-opensuse/build/build-st-9429/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-qemux86-64-20181126235134.rootfs.cpio cpio shouldn't be crashing, ever, but was this triggered by the image changing underneath it?
Turns out this is a bug in the latest CVE patch to cpio, so if either: 1) cpio-native was installed in the sysroot, or 2) the host has the CVE patch present Then cpio will segfault when appending to an archive. I've patches that I shall submit when cleaned up.
Merged in oe-core c3b9aedcbe538d7fa74bd814644b4899769dec46.