[OE-core] Yocto Project Status WW51’17

[Randy MacLeod]

On 2017-12-18 10:52 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.5 M2 development
> 
> Next Deadline: YP 2.5 M2 cut off of 1/15/18
> 
> SWAT team rotation: Stephano -> Maxin on Dec. 15, 2017.
> 
> SWAT team rotation: Maxin -> Cal on Dec. 22, 2017.
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> Key Status/Updates:
> 
> ·The QA of YP 2.5 M1 rc1 is just starting.  See: 
> https://wiki.yoctoproject.org/wiki/2.5_QA_Status
> 
> ·The QA of YP 2.4.1 rc1 is about 80% complete.  See: 
> https://wiki.yoctoproject.org/wiki/2.4_QA_Status. We are having some 
> issues with the eclipse plugin testing.
> 
> ·The QA of YP 2.3.3 rc1 is about 3% complete. See: 
> https://wiki.yoctoproject.org/wiki/2.3_QA_Status
> 
> ·YP 2.2.3 rc1 has been built and is queued to begin QA when the QA team 
> has bandwidth.
> 
> ·We have finally tracked down the qemux86-64 kvm apic hang to an issue 
> in the host kernel. We have a mitigation plan in mind but that is 
> blocked on finding another separate bug causing selftest failures when 
> upgrading the guest kernel.
> 
> ·We have identified further intermittent bugs in various releases which 
> we’re continuing to look into (including gpg memory allocation issues on 
> pyro, sstate writing races in morty, further occurrences of the inode 
> count issues with our NAS on the autobuilder).

If any of the new problems prove to be difficult to debug, please
reply with the defect ID so that people can read the background
and perhaps help out in some way.

WR used to use a single large NAS for our build cluster 3+ years ago.
While it worked to first order, there was a background of mysterious
errors. We switch to local disks and pushing logs/status to
a centralized git repo and we've been happy with that choice.
-- 
# Randy MacLeod.  WR Linux
# Wind River an Intel Company