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.

Nightly 524

• master-next fired by RP
• Test of patches from mailing list
• nightly-ipk opkg failure reported on list to opkg patch sender

Nightly 523

• master-next fired by RP
• DOA due to bitbake bug, replied on list about patch issue to Alex Franco

Nightly 522

• master fired by RP
• test current status after merging various patches
• nightly-deb sanitytest2 failure: #8061 "Occasional qemux86 segfault"
• nightly-arm sanitytest failure: #8234 (same testimage fails as some previous builds)
• nightly-mips sanitytest failure: #8139 "smart failures occur ... on several builders"

Nightly 521

• poky:master fired by halstead for testing build failure mails
• nightly-arm-lsb (core-image-lsb-sdk) testimage failure #8234
• RP killed in favour of 522

Nightly 520

• poky:master-next fired by pidge
• Test mailing list submissions merged into master-next
• Test some bugfixes that went into master
• ccache build failure (upgrade related) reported by RP on mailing list
• Race between a qa check and packaging reported in ML thread Add checks for "host user contamination"
• imagetest timeout #8229
• toaster upload failures (and strange successes) #8230

Nightly 519

• master fired by RP
• Test master status after merge of various fixes.
• nightly-arm-lsb segfault looks like #8060
• nightly-arm-lsb error submission failure #8225
• autobuilder current link not set when set to not publish artifacts #8226
• wic issue in nighttly-oe-selftest reported to Ed
• Need to look into second image failure for nightly-mips-lsb (on edgerouter), failed after 2 seconds, no error shown
• Need to look into nightly-mips-lsb sanity test failure (command timeout)

Nightly 518

• master fired by RP
• Try and figure out where we are having merged patches from various places
• failure in nightly-ppc-lsb due to incorrect SRCREV in 3.14 kernel recipe (attempted fix merged)
• failure in nightly-mips-lsb in linux-yocto -3.14 do_patch reported to Bruce, *also* edgerouter issue with compile failure (not reported, need bug)
• failure in nightly-oe-selftest due to dump.py oeqa changes (workaround merged)
• failure in mightly-mips due to random smart test failures (bug needed)
• failure in nightly-x86 due to qemu thread kick issue, bactrace still corrupt but may be decodable using TMPDIR on AB. [RP added notes to 8143 with backtrace info]

Nightly 517

• ross/mut2 fired by Ross
• Patch sweep from oe-core
• Includes Bruce's kernel patches, will break as 515 did
• nightly-arm SDK fail - transient sourceforge fetch failure (change test URL to YP mirror?) (need bug)
• nightly-arm-lsb, nightly-fsl-arm-lsb, nightly-world-lsb, nightly-x86-lsb, nightly-x86_64-lsb - busybox compile failure (Khem's patch?)
• nightly-deb - kernel segfault in sanity test (need bug)
• nightly-mips - smart sanity test issues (need bug)
• nightly-systemd-qa - two different failures, date issue and avahi (same as previous build) (need bug)
• nightly-oe-selftest - two issues, one function parameter change and one from the new test (patch from Mariano and RP likely at fault)

Nightly 515

• ross/mut fired by Ross
• Most of master-next rebased upon ross/for-master (fixes to make master mostly build green)
• Should be green.
• oe-selftest: failed in devtool (fixed in updated mut)
• mips-lsb, x86-lsb: kernel sanity test fails
• mips-lsb: specific kernel build failed (#8224, master also)
• ppc-lsb: kernel 3.14 fetch fail
• multilib: sanity test failed (#8219, fixed in updated mut)
• systemd: qemu_cpu_kick_thread (#8143)
• Conclusion: drop kernel patches, merged updated ross/mut (not mut2)

Nightly 505

• ross/mut-next, experimental sweep of patches from the list
• BOOM

Nightly 503

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/503
• Lucky five hundred and three!
• Triggered by Ross (ross/mut)
• Build 500 plus a LSB test suite fix, should be 100% green
• Aborted!

Nightly 500

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/500
• Lucky five hundred?
• Triggered by Ross (ross/qemu)
• Just master plus Anibal's qemu poll patch

Nightly 499

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/499
• Triggered by Ross (ross/mut)
• Test of patches from mailing list
• Including Randy's qemu fix!
• Won't force push this time, should build 100% green

Nightly 497

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/497
• Triggered by Ross (ross/mut)
• Test of patches from mailing list
• Many failures due to a force push during build (8195 8196)

Nightly 492

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/492
• Triggered by Beth for Ross (ross/mut)
• Test of patches from mailing list
• SWAT: Needs bugs for lsb test image failures and systemd failure (mention on related bug)

Nightly 489

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/489
• Triggered by Beth for RP (master-next)
• Test of gcc 5.x, also keep AB loaded to try and reproduce 'random' failures with new logging
• SWAT: Need bug for weston failure in nightly-world (https://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/450/steps/BuildImages/logs/stdio)
• SWAT: Need bug for qemuarm hang with gcc 5.x (if not one already, assign to Bruce Ashfield)

Nightly 483

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/483
• Triggered by RP
• Test of gcc 5.x, also keep AB loaded to try and reproduce 'random' failures with new logging

Nightly 482

• Incorrectly setup, immediate abort

Nightly 481

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/481
• Triggered by RP
• upgrades and other improvements to test their status
• includes test of glibc upgrade which may have issues
• Successful - merged to master

Nightly 480

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/480
• Triggered by RP
• upgrades and qemu improvements to test their status
• includes test of glibc upgrade which may have issues
• Aborted by RP due to boot issues, suspect nfs-utils

Nightly 479

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/479
• Triggered by RP
• upgrades and qemu improvements to test their status
• includes test of glibc upgrade which may have issues
• do_rootfs failures from rpm/db upgrade, aborted build due to this

Nightly 478

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/478
• Triggered by RP for Ross
• master plus "safe" upgrades and qemu improvements
• Successful - merged to master

Nightly 477

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/477
• Triggered by Ross
• master plus "safe" upgrades and qemu improvements

Nightly 475

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/475
• Triggered by Ross
• 473 without openssh, should build green.
• Include the qemu_cpu_kick_thread debugging

Nightly 473

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/473
• Triggered by Ross
• 472 without the ext4 patches to determine if they broke sanity

Nightly 472

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/472
• Triggered by Ross
• Mainly to test glibc 2.22

Nightly 471

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/471
• Triggered by Ross
• Mostly patches from oe-core list, lots of upgrades.

Nightly 469

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/469
• master build destined to become 1.9M2.rc2.
• has fixes for pam issue, fedora22 runqemu issues, weston parallel make race

Nightly 468

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/468
• master-next triggered by RP to test fix for fedora22 runqemu issues

Nightly 467

• https://autobuilder.yoctoproject.org/main/builders/nightly/builds/467
• master-next triggered by RP to test incoming changes from mailing list
• SWAT Status: All issues show were not due to master-next and therefore bugs need to be filed.