Weekly Status: Difference between revisions
Line 9: | Line 9: | ||
'''Key Status/Updates:'''<br/> | '''Key Status/Updates:'''<br/> | ||
* | *We are now two weeks away from feature freeze for 4.3. | ||
*YP 3.1.27 was | *YP 3.1.27 was released | ||
* | *YP 4.0.12 is in QA. | ||
*The 6.4 kernel upgrade is still blocked as we’ve seen two nasty looking hangs in automated testing: | |||
*There are | https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/349/steps/12/logs/stdio | ||
* | https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/354/steps/12/logs/stdio | ||
as well as a preempt-rt boot error that appears more consistently: | |||
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7616/steps/36/logs/stdio | |||
The intermittent issues are a significant risk to automated testing stability and it is hard to know how to proceed as few people are willing/able to help with them. We’ve upgraded qemu 8.0.3 -> 8.0.4 just in case that helps. | |||
The various systemd issues have mostly been resolved although the AUH did break as a result and will have to be fixed and rerun. | |||
Build layout changed slightly with the removal of PE and PR from the WORKDIR path. | |||
There are patches pending which remove source control revisions from PV and move them to PKGV, further simplifying WORKDIR paths and generally improving the code and the way AUTOREV works. This allows SRCPV to be removed as it is no longer needed. | |||
*Significant fixes were made to both the binutils and gcc testsuites which avoid many of the mips toolchain test failures. The failure counts are roughly the same (few hundred) for each architecture now resulting in ~3200 failures overall. | |||
*There are now consistently ~200 ltp ‘controllers’ failures on both arm and x86 targets. | |||
*A new uninative version was released to add some patches to patchelf to avoid bugs. | |||
*A new test addition to oe-selftest caused another test to fail consistently on the autobuilder and this has been tracked down to one test corrupting the other if they run in the same TMPDIR. This only happens with specific parallelism settings where they happen to run together or with no parallelism. | |||
*We continue to see intermittent ptest failures for glib-networking, mdadm and openssh, help would be much appreciated. | |||
*CVE metrics are worrying with significant numbers of open CVEs against master, many of them kernel related. The 6.4 upgrade should help but that is blocked. Mickledore is also badly affected with a record high count. https://autobuilder.yocto.io/pub/non-release/patchmetrics/ | *CVE metrics are worrying with significant numbers of open CVEs against master, many of them kernel related. The 6.4 upgrade should help but that is blocked. Mickledore is also badly affected with a record high count. https://autobuilder.yocto.io/pub/non-release/patchmetrics/ | ||
Revision as of 14:47, 15 August 2023
Yocto Project Weekly Status August 15th, 2023
Current Dev Position: YP 4.3 M3
Next Deadline: 28th August 2023 YP 4.3 M3 build date
Next Team Meetings:
- Bug Triage meeting Thursday August 17th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Weekly Engineering Sync Tuesday August 15th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
- We are now two weeks away from feature freeze for 4.3.
- YP 3.1.27 was released
- YP 4.0.12 is in QA.
- The 6.4 kernel upgrade is still blocked as we’ve seen two nasty looking hangs in automated testing:
https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/349/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/354/steps/12/logs/stdio as well as a preempt-rt boot error that appears more consistently: https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7616/steps/36/logs/stdio The intermittent issues are a significant risk to automated testing stability and it is hard to know how to proceed as few people are willing/able to help with them. We’ve upgraded qemu 8.0.3 -> 8.0.4 just in case that helps. The various systemd issues have mostly been resolved although the AUH did break as a result and will have to be fixed and rerun. Build layout changed slightly with the removal of PE and PR from the WORKDIR path. There are patches pending which remove source control revisions from PV and move them to PKGV, further simplifying WORKDIR paths and generally improving the code and the way AUTOREV works. This allows SRCPV to be removed as it is no longer needed.
- Significant fixes were made to both the binutils and gcc testsuites which avoid many of the mips toolchain test failures. The failure counts are roughly the same (few hundred) for each architecture now resulting in ~3200 failures overall.
- There are now consistently ~200 ltp ‘controllers’ failures on both arm and x86 targets.
- A new uninative version was released to add some patches to patchelf to avoid bugs.
- A new test addition to oe-selftest caused another test to fail consistently on the autobuilder and this has been tracked down to one test corrupting the other if they run in the same TMPDIR. This only happens with specific parallelism settings where they happen to run together or with no parallelism.
- We continue to see intermittent ptest failures for glib-networking, mdadm and openssh, help would be much appreciated.
- CVE metrics are worrying with significant numbers of open CVEs against master, many of them kernel related. The 6.4 upgrade should help but that is blocked. Mickledore is also badly affected with a record high count. https://autobuilder.yocto.io/pub/non-release/patchmetrics/
Ways to contribute:
- As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
- There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
- There are bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
- We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
- Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
- Help us resolve CVE issues: CVE metrics
- We have a growing number of bugs in bugzilla, any help with them is appreciated.
YP 4.3 Milestone Dates:
- YP 4.3 M3 build date 2023/08/28
- YP 4.3 M3 Release date 2023/09/08
- YP 4.3 M4 build date 2023/10/02
- YP 4.3 M4 Release date 2023/10/27
Upcoming dot releases:
- YP 3.1.27 is released
- YP 4.0.12 is in QA
- YP 4.0.12 Release date 2023/08/18
- YP 4.2.3 build date 2023/08/28
- YP 4.2.3 Release date 2023/09/08
- YP 3.1.28 build date 2023/09/18
- YP 3.1.28 Release date 2023/09/29
- YP 4.0.13 build date 2023/09/25
- YP 4.0.13 Release date 2023/10/06
- YP 3.1.29 build date 2023/10/30
- YP 3.1.29 Release date 2023/11/10
- YP 4.0.14 build date 2023/11/06
- YP 4.0.14 Release date 2023/11/17
- YP 4.2.4 build date 2023/11/13
- YP 4.2.4 Release date 2023/11/24
- YP 3.1.30 build date 2023/12/11
- YP 3.1.30 Release date 2023/12/22
- YP 4.0.15 build date 2023/12/18
- YP 4.0.15 Release date 2023/12/29
Tracking Metrics:
- WDD 2463 (last week 2495) (https://wiki.yoctoproject.org/charts/combo.html)
- OE-Core/Poky Patch Metrics
- Total patches found: 1186 (last week 1186)
- Patches in the Pending State: 255 (22%) [last week 256 (22%)]
- https://autobuilder.yocto.io/pub/non-release/patchmetrics/
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC