Yocto Project Status WW34

Yocto Project Status WW34

[Saul Wold]

[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]



Current Dev Position: YP 2.2 M3
Next Deadline: YP 2.2 M3 which will be Aug 29th (5:00pm GMT)

SWAT team rotation: Juro -> Anibal
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:
 * We’re drawing close to the M3 deadline and feature freeze for 2.2. There is still a significant number of features outstanding with several looking to be at risk at this point.
 * The bitbake multi-config build series has now merged. 
 * We’ve re-enabled prelink on x86/mips. ppc/arm was disabled whilst we investigated test failures but will likely be enabled since the issues are looking to be a binutils bug.
 * We upgraded to gcc 6.2rc1 (we will track 6.2 through to our release)
 * Uninative 1.3 was released to deal with some locale problems. This will need to be backported to krogoth as a 1.0.1 release of uninative.
 * Current master is going to go through a full QA pass before M3 to try and make sure we are dealing with all the known bugs.
 * We are starting to see significant ‘random’ autobuilder failures again:
    * Mips machine ‘failure to start’ despite booting the kernel: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10136
    * Systemd logging failure: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128
    * Unknown ppc failure: https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/910/steps/Running%20Sanity%20Tests/logs/stdio
    * Uvesa timeout issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8245
    * Busybox parallel make race: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10116
We need to get to grips with these as a matter of urgency as they do keep recurring and several occurred during our QA build, sadly. I am getting quite concerned about these.
 * 2.1.1 has been released, finally!
 * We will be moving to the 4.7 kernel before M3 closes, and evaluating a move to 4.8 in mid-September.  We will be keeping both the 4.1 (as LTSI) and 4.4 (as LTS) kernels.  GregKH has announced that 4.9 will be the next LTS for a Dec/Jan release, therefore our 4.7 (or 4.8) will be short lived kernels.

Key YP 2.2 Dates:
 * YP 2.2 M1 release would be: 6/24/16
 * YP 2.2 M2 cut off would be: 7/18/16
 * YP 2.2 M2 release would be: 7/29/16
 * YP 2.2 M3 cut off would be: 8/29/16
 * YP 2.2 M3 release would be: 9/9/16
 * YP 2.2 M4 cut off would be: 10/3/16
 * YP 2.2 M4 release would be: 10/28/16

Tracking Metrics:
	WDD 2706  (last week 2712)
(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

[-- Attachment #2: Type: text/html, Size: 17641 bytes --]

Yocto Project Status WW34

[Jolley, Stephen K]

[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]

Current Dev Position: 1.9 Milestone 3 (M3)
Next Deadline: M3 cut off of August 24th at noon GMT

SWAT team rotation: Tracy -> Alejandro
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

  *   The autobuilder situation has become problematic as it appears some things we think are being built are not what is actually being built. We're looking into the scope of the issue, we're hoping it's contained within a small subset of builds and the milestone/master releases are not affected but this yet to be confirmed.
  *   We did add automated runtime testing of the SDK (-c testsdk) and automated runtime testing of LSB images which wasn't previously being tested. This significantly increases the automated coverage of project artefacts.
  *   We have a potential fix for the "qemu networking hang" which turns out to be a qemu serial port issue, thanks to Randy for figuring that out!
  *   We also have a lead on the systemd ttyS0 failure to start (thanks Anibal!) and a way to reproduce it but no fix yet for it.
  *   The autobuilder situation combined with everything else means patches are delaying being merged and the M3 release cutoff/feature freeze will be delayed.
  *   RP is on vacation for the second half of next week.

Key YP 1.9 Dates:
YP Final - 2.0 Cut off: Sept. 28, 2015 noon GMT
1.9 M3 Release Target: Before Sept. 11 2015
2.0 final Release Target: Before Oct. 30, 2015

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status
https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features

Tracking Metrics:
            WDD 1950 (last week 1889 )
(https://wiki.yoctoproject.org/charts/combo.html)

[If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:          (503) 712-0534
*    Cell:                                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 22440 bytes --]