9577 2016-05-03 14:42:33 +0000 gen-lockedsig-cache fails when populating sdk ext on PPC architecture 2016-09-15 15:22:15 +0000 1 1 10 QA/Testing Build Testing general 2.2 x86 Multiple RESOLVED WORKSFORME Medium+ normal 2.2 M3 1 leonardo.sandoval.gonzalez Qi.Chen bluelightning richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 61897 0 leonardo.sandoval.gonzalez 2016-05-03 14:42:33 +0000 This problem was found on the AB [1] Exception: ExecutionError: Execution of 'gen-lockedsig-cache /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/sdk-ext/image//opt/poky/2.1+snapshot/conf/locked-sigs.inc /srv/www/vhosts/autobuilder.yoctoproject.org/pub/sstate/ /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/sdk-ext/image//opt/poky/2.1+snapshot/sstate-cache universal' failed with exit code 1: Reading /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/sdk-ext/image//opt/poky/2.1+snapshot/conf/locked-sigs.inc Gathering file list Processing files . . . Processing /srv/www/vhosts/autobuilder.yoctoproject.org/pub/sstate//fa/sstate:busybox::1.24.1:r0::3:fa7b2b4f51d3e23d7e26e37334d5d08a_populate_lic.tgz.siginfo... Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-ppc/build/scripts/gen-lockedsig-cache", line 50, in <module> if (os.stat(f).st_dev == os.stat(destdir).st_dev): OSError: [Errno 2] No such file or directory: '/srv/www/vhosts/autobuilder.yoctoproject.org/pub/sstate//fa/sstate:busybox::1.24.1:r0::3:fa7b2b4f51d3e23d7e26e37334d5d08a_populate_lic.tgz.siginfo' [1] https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/763 61904 1 bluelightning 2016-05-03 17:17:22 +0000 It can't be a coincidence that this is the same task we're seeing as missing with bug 9575. 66214 2 richard.purdie 2016-09-15 15:22:15 +0000 We're not seeing this issue on the autobuilder any more so I assume this was fixed at some point and the bug just got lost in the system. Resolving accordingly.