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 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.