Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(304 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 25, 2021 ==
== Yocto Project Weekly Status May 28th, 2024 ==
Current Dev Position: YP 3.4 M1<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 7th June 2021 YP 3.4 M1 build<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 27th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday May 30th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday June 1st at 8am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday May 28th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 8th at 8am PDT (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/>
*YP 3.3.1 was released
*YP 5.0.1 has been released.
*YP 3.1.8 is being built, an autobuilder glitch meant we’re building rc2.
*We have suspected a performance problem for a while, this has now been identified/confirmed as an issue with hash equivalence. The public server using websockets/SSL has significantly slowed down things, to the point a 2 hour world build is taking 18+ hours. In trying to improve this, we ended up destablising the autobuilders entirely, breaking many builds and halting the patch merging.
*We’ve seen a significant reduction in CVE counts for master and the stable releases this week. For master this brings us down to 5 CVEs compared to 63 a couple of weeks ago. This should mean real/open issues are much clearer and old/obsolete issues no longer contribute noise to the output of the tools.
The problem is visible both at build initialization time and also at any point it rehashes due to new hash information from the server. We are still trying to work out ways to improve things but there appears to be multiple levels of different problems, including the hashserve client parallelism seeming to have bugs. The issue affects scarthgap as well as master.
*Help with the problematic recipe upgrades would be much appreciated.
*A new gcc 14 compatible version of uninative was released allowing fedora 40 testing. Unfortunately there are issues with build failures on that host that are as yet uninvestigated.
*The multiconfig changes in bitbake continue to cause problems, we still need simpler test cases to reproduce issues rather than huge builds. The existing patches seem to fix some workloads and break others. Richard is trying to fix but trying to fix autobuilder issues and other problems and these are slow builds to debug.
*The WORKDIR to UNPACKDIR transition has merged and other layers are now working on the updates needed. There appear to be some challenges around go modules in particular which are needing more investigation and development time.
*We have identified ltp issues with some tests causing hangs which have been disabled as well as issues with the 5.10.37 kernel which seem to be fixed in 5.10.38.
*We aim to build YP 5.1 M1 after the performance issue is addressed and we have stable builds.
*We’re seeing odd looking rcu stalls in qemu automated testing. This seems to occur more often with 5.10 kernel but also with 5.12 and with kvm-clock disabled and we have seen it with 5.4. It is unclear whether these are kernel issues or qemu issues, we’re struggling to debug them and any insight would be welcome.
*We were able to merge a chunk of pending patches but things are still processing slowly unfortunately.
*Some debugging of these intermittent hangs has been posted to the swat mailing list.
*There are some CVE related announcements which are helpful to us:
*Intermittent autobuilder issues continue to occur and are now at a record high level. 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 We are working to identify the load pattern on the infrastructure that seems to trigger these.
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
**Unfortunately there are reports that the backlog of CVEs without version constraints is growing rapidly
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
**Please consider signing this to show support for those changes.
**Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
*The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal, also not helped with the performance issue identfiied above.
*Further performance graph improvements have merged and the graphs now have links to specific revisions allowing regressions to be much more easily tracked down.


'''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: 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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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 us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 3.4 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.4 M1 build date 2021/06/07
*WDD 2772 (last week 2752) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.4 M1 Release date 2021/06/18
*OE-Core/Poky Patch Metrics
*YP 3.4 M2 build date 2021/07/12
**Total patches found: 1121 (last week 1127)
*YP 3.4 M2 Release date 2021/07/23
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*YP 3.4 M3 build date 2021/08/23
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 3.4 M3 Release date 2021/09/03
*YP 3.4 M4 build date 2021/10/04
*YP 3.4 M4 Release date 2021/10/29


'''Planned upcoming dot releases:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 3.3.1 is in released
*YP 5.1 M1 Build date 2024-05-20
*YP 3.1.8 is being built
*YP 5.1 M1 Release date 2024-05-31
*YP 3.1.8 release date 2021/06/04
*YP 5.1 M2 Build date 2024-07-08
*YP 3.1.9 build date 2021/06/21
*YP 5.1 M2 Release date 2024-07-19
*YP 3.1.9 release date 2021/07/02
*YP 5.1 M3 Build date 2024-08-26
*YP 3.3.2 build date 2021/07/19
*YP 5.1 M3 Release date 2024-09-06
*YP 3.3.2 release date 2021/07/30
*YP 5.1 M4 Build date 2024-09-30
*YP 3.1.10 build date 2021/07/26
*YP 5.1 M4 Release date 2024-10-25
*YP 3.1.10 release date 2021/08/06
*YP 3.1.11 build date 2021/09/13
*YP 3.1.11 release date 2021/9/24


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2647 (last week 2664) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.1 is released.
*Poky Patch Metrics 
*YP 4.0.19 build date 2024-06-03
**Total patches found: 1282 (last week 1297)
*YP 4.0.19 Release date 2024-06-14
**Patches in the Pending State: 491 (38%) [last week 494 (38%)]
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29


'''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 58: Line 78:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 14:40, 28 May 2024

Yocto Project Weekly Status May 28th, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0.1 has been released.
  • We have suspected a performance problem for a while, this has now been identified/confirmed as an issue with hash equivalence. The public server using websockets/SSL has significantly slowed down things, to the point a 2 hour world build is taking 18+ hours. In trying to improve this, we ended up destablising the autobuilders entirely, breaking many builds and halting the patch merging.

The problem is visible both at build initialization time and also at any point it rehashes due to new hash information from the server. We are still trying to work out ways to improve things but there appears to be multiple levels of different problems, including the hashserve client parallelism seeming to have bugs. The issue affects scarthgap as well as master.

  • A new gcc 14 compatible version of uninative was released allowing fedora 40 testing. Unfortunately there are issues with build failures on that host that are as yet uninvestigated.
  • The WORKDIR to UNPACKDIR transition has merged and other layers are now working on the updates needed. There appear to be some challenges around go modules in particular which are needing more investigation and development time.
  • We aim to build YP 5.1 M1 after the performance issue is addressed and we have stable builds.
  • We were able to merge a chunk of pending patches but things are still processing slowly unfortunately.
  • There are some CVE related announcements which are helpful to us:
    • There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
    • CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
    • Unfortunately there are reports that the backlog of CVEs without version constraints is growing rapidly
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
    • Please consider signing this to show support for those changes.
    • Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
  • The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
  • The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal, also not helped with the performance issue identfiied above.
  • Further performance graph improvements have merged and the graphs now have links to specific revisions allowing regressions to be much more easily tracked down.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 5.0.1 is released.
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29

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=86341"