BuildLog

This is a rolling log of builds being run on the autobuilder. The person triggering the build should note here what the expectations of the build are. Anyone following up on that build (such as the SWAT team) should note what they've done about any failures. Ordering is more recent at the top.

https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/607/steps/Running%20Sanity%20Tests/logs/stdio

nightly 586 - master-next 28747dcfbf21a80416d655eac5f8494fbea28f87

Build ID - 28747dcfbf21a80416d655eac5f8494fbea28f87 on new cluster
Started at: Sun Oct 8 23:15:39 2017
A build was forced by 'richard <richard@localhost>'
Test changes in -next potentially for rc2
nightly failed:
- BitbakeSelftest
- wget fetcher tests fail with:

FAIL: test_wget_checkstatus (bb.tests.fetch.FetchCheckStatusTest)

Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build/bitbake/lib/bb/tests/fetch.py", line 840, in test_wget_checkstatus
    self.assertTrue(ret, msg="URI %s, can't check status" % (u))
AssertionError: False is not true : URI ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.60.tar.gz, can't check status


FAIL: test_wget_checkstatus_connection_cache (bb.tests.fetch.FetchCheckStatusTest)

Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build/bitbake/lib/bb/tests/fetch.py", line 854, in test_wget_checkstatus_connection_cache
    self.assertTrue(ret, msg="URI %s, can't check status" % (u))
AssertionError: False is not true : URI ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.60.tar.gz, can't check status

nightly-refkit failed:
- BuildImages
- During refkit-image-computervision-1.0-r0 do_rootfs:

ERROR: refkit-image-industrial-1.0-r0 do_rootfs: Unable to install packages. Command '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-industrial/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-industrial/1.0-r0/opkg.conf -t /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-industrial/1.0-r0/temp/ipktemp/ -o /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-industrial/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   install linux-firmware packagegroup-core-ssh-openssh packagegroup-core-boot run-postinsts alsa-utils lms8 packagegroup-industrial-robotics alsa-state kernel-modules packagegroup-common-test packagegroup-core-connectivity' returned 1:
Collected errors:
 * Solver encountered 1 problem(s):
 * Problem 1/1:
 *   - nothing provides linux-firmware-imx-sdma-license needed by linux-firmware-1:0.0+git0+a61ac5cf83-r0.all
 * 
 * Solution 1:
 *   - do not ask to install a package providing linux-firmware

nightly-x86-64 failed:
- BuildImages_2
- During core-image-sato-1.0-r0 do_rootfs

<wiki>Package xkeyboard-config-locale-en-gb-2.21-r0.0.core2_64 from local repository oe-repo has incorrect checksum

Error: Some packages from local repository have incorrect checksum</wiki>

- Running ESDK Sanity Tests
- Failed because the eSDK wasn't built, as above

nightly 585 - akuster/pyro-next 9ce4bcc24e06f2f67d1b024bda80a63ca53f62ac

Build ID - 9ce4bcc24e06f2f67d1b024bda80a63ca53f62ac on new cluster
Started at: Sun Oct 8 20:43:23 2017
A build was forced by 'akuster <akuster@localhost>'
akuster/pyro-next system check, ran out of disk space before [swat I will monitor]
nightly-multilib failed:
- BuildImages_2
- Running Sanity Tests_2