STATUS: IDLE BUILD: 2.1.3: rc1-fe7fb002216f7886d49942333ea6d8592339bb05 ENVIRONMENT:Autobuilder EXPECTED OUTCOME: WIC images present and ready to download ACTUAL OUTCOME: There are not WIC images for genericx86 or genericx86-64 Images must be present here: https://autobuilder.yocto.io/srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.1.3.rc1/machines/
Looking at the logs for nightly-wic[1] we can see that the images are being created, i.e.e genericx86-64[2]: Creating image(s)... Info: The new image(s) can be found here: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/deploy/wic_images/genericx86-64/directdisk/core-image-sato/build/directdisk-201706070814-sda.direct The following build artifacts were used to create the image(s): ROOTFS_DIR: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/work/genericx86_64-poky-linux/core-image-sato/1.0-r0/rootfs BOOTIMG_DIR: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/sysroots/genericx86-64/usr/share KERNEL_DIR: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/deploy/images/genericx86-64 NATIVE_SYSROOT: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/sysroots/x86_64-linux The image(s) were created using OE kickstart file: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/scripts/lib/wic/canned-wks/directdisk.wks Unless I'm misreading things it looks like the PublishArtifacts step[3] is copying things from the right location to the correct destination: mkdir -p /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.1.3.rc1/machines/genericx86-64; cp --no-dereference --preserve=links /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/deploy/wic_images/genericx86-64/*/*/build/*\.direct /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-wic/build/build/tmp/deploy/wic_images/genericx86-64/*/*/build/*\.direct.md5sum /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.1.3.rc1/machines/genericx86-64|| export PA_FAIL=1; if [ "$PA_FAIL" = "1" ]; then exit 1; As the buildstep is marked as succeeded we know the PA_FAIL variable wasn't set and therefore the copy appears to have succeeded. 1. https://autobuilder.yocto.io/builders/nightly-wic/builds/308 2. https://autobuilder.yocto.io/builders/nightly-wic/builds/308/steps/CreateWicImages_8/logs/stdio 3. https://autobuilder.yocto.io/builders/nightly-wic/builds/308/steps/Publishing%20Artifacts/logs/stdio
The directdisk-201706070814-sda.direct the logs report creating exists at https://autobuilder.yocto.io/srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.1.3.rc1/machines/genericx86-64/directdisk-201706070814-sda.direct
The autobuilder has the .direct images this are used instead of wic on 2.1
I miss calculated the magnitude of this, and thought that if the .direct images were present we could close this. It seems that images are not in the right path and we are getting weird behaviors when tested.
.wic images are generated by the build system when building images with bitbake and the .direct images are generated by the nightly-wic builder which invokes wic directly. Generating .wic images wasn't enabled by default in krogoth, that's why 2.1.x builds don't include .wic files. For example see the 2.1.1 and 2.1.2 builds: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.1/machines/genericx86-64/ http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/machines/genericx86-64/
.wic images aren't expected to be generated for krogoth builds
not tested .wic in krogoth