Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(119 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 15th, 2023 ==
== Yocto Project Weekly Status Mar. 11th, 2025 ==
Current Dev Position: YP 4.3 M3<br/>
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday August 17th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 15th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Mar. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester  


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now two weeks away from feature freeze for 4.3.
*YP 5.1.3 was released
*YP 3.1.27 was released
*YP 5.2 M3 is in QA
*YP 4.0.12 is in QA.
*YP 5.0.8 is ready for 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.
*We are now at feature freeze for YP 5.2
*The various systemd issues have mostly been resolved although the AUH did break as a result and will have to be fixed and rerun.
*We have a new dashboard index page linking to key tools/data pages within the project: https://dashboard.yoctoproject.org/ . Help on further improvements is welcome. We are aiming to drive the data from the autobuilder.
*Build layout changed slightly with the removal of PE and PR from the WORKDIR path.
*An infrastructure issue where git mirroring was stalling has been fixed
*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.
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
*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.  
*The buildbot workers display has been fixed to allow more builds to be shown and an autobuilder build scheduling issue has been resolved allowing better resource utilization.
*There are now consistently ~200 ltp ‘controllers’ failures on both arm and x86 targets.
*We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
*A new uninative version was released to add some patches to patchelf to avoid bugs.
*There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
*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.
*A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
*We continue to see intermittent ptest failures for glib-networking, mdadm and openssh, help would be much appreciated.
*Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
*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/
*Emails have been sent about the CVE/NVD situation proposing a path forward.
*The gomod mirror issue in meta-openembedded was continuing to give failed builds on the autobuilder.The patch has been reverted in meta-openembedded for now to regain stable builds. Warnings were creeping in whilst the error was masking them. We need to fix the root cause.
*Our own systemctl python script has been replaced with the correct tool for better compatibility
*We’ve identified a significant increase in build disk usage from the rust upgrade.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*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!
*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: 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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*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.
*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 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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''YP 4.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.3 M3 build date  2023/08/28
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.3 M3 Release date 2023/09/08
*OE-Core/Poky Patch Metrics
*YP 4.3 M4 build date  2023/10/02
**Total patches found: 1027 (last week 1024)
*YP 4.3 M4 Release date 2023/10/27
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.2 M3 in QA.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.27 is released
*YP 5.1.3 was released,
*YP 4.0.12 is in QA
*YP 5.0.8 is waiting for QA.
*YP 4.0.12 Release date 2023/08/18
*YP 5.1.4 Build Date 2025-03-24
*YP 4.2.3 build date 2023/08/28
*YP 5.1.4 Release Date 2025-04-04
*YP 4.2.3 Release date 2023/09/08
*YP 4.0.26 Build Date 2025-04-07
*YP 3.1.28 build date 2023/09/18
*YP 4.0.26 Release Date 2025-04-18
*YP 3.1.28 Release date 2023/09/29
*YP 5.0.9 Build Date 2025-04-21
*YP 4.0.13 build date 2023/09/25
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.13 Release date 2023/10/06
*YP 4.0.27 Build Date 2025-05-19
*YP 3.1.29 build date 2023/10/30
*YP 4.0.27 Release Date 2025-05-30
*YP 3.1.29 Release date 2023/11/10
*YP 5.0.10 Build Date 2025-06-02
*YP 4.0.14 build date 2023/11/06
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.14 Release date 2023/11/17
*YP 4.0.28 Build Date 2025-06-30
*YP 4.2.4 build date 2023/11/13
*YP 4.0.28 Release Date 2025-07-11
*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:'''<br/>
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 70: Line 69:


== Archives ==
== Archives ==
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

Latest revision as of 14:50, 11 March 2025

Yocto Project Weekly Status Mar. 11th, 2025

Current Dev Position: YP 5.2 M4 - Feature Freeze
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze

Next Team Meetings:

Key Status/Updates:

  • YP 5.1.3 was released
  • YP 5.2 M3 is in QA
  • YP 5.0.8 is ready for QA
  • We are now at feature freeze for YP 5.2
  • We have a new dashboard index page linking to key tools/data pages within the project: https://dashboard.yoctoproject.org/ . Help on further improvements is welcome. We are aiming to drive the data from the autobuilder.
  • An infrastructure issue where git mirroring was stalling has been fixed
  • There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
  • The buildbot workers display has been fixed to allow more builds to be shown and an autobuilder build scheduling issue has been resolved allowing better resource utilization.
  • We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
  • There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
  • A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
  • Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
  • Emails have been sent about the CVE/NVD situation proposing a path forward.
  • The gomod mirror issue in meta-openembedded was continuing to give failed builds on the autobuilder.The patch has been reverted in meta-openembedded for now to regain stable builds. Warnings were creeping in whilst the error was masking them. We need to fix the root cause.
  • Our own systemctl python script has been replaced with the correct tool for better compatibility
  • We’ve identified a significant increase in build disk usage from the rust upgrade.

Ways to contribute:

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M3 in QA.
  • YP 5.2 M4 Build Date 2025-03-31
  • YP 5.2 M4 Release Date 2025-04-25

Upcoming dot releases:

  • YP 5.1.3 was released,
  • YP 5.0.8 is waiting for QA.
  • YP 5.1.4 Build Date 2025-03-24
  • YP 5.1.4 Release Date 2025-04-04
  • YP 4.0.26 Build Date 2025-04-07
  • YP 4.0.26 Release Date 2025-04-18
  • YP 5.0.9 Build Date 2025-04-21
  • YP 5.0.9 Release Date 2025-05-02
  • YP 4.0.27 Build Date 2025-05-19
  • YP 4.0.27 Release Date 2025-05-30
  • YP 5.0.10 Build Date 2025-06-02
  • YP 5.0.10 Release Date 2025-06-13
  • YP 4.0.28 Build Date 2025-06-30
  • YP 4.0.28 Release Date 2025-07-11

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86582"