Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(540 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status February 12, 2019 ==
== Yocto Project Weekly Status May 28th, 2024 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 30th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday May 28th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


*SWAT lead is currently: Paul
'''Key Status/Updates:'''<br/>
*SWAT team rotation: Paul -> Ross on Feb. 15, 2019
*YP 5.0.1 has been released.
*SWAT team rotation: Ross -> Amanda on Feb. 22, 2019
*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.
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
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.


'''Key Status/Updates:'''<br/>
'''Ways to contribute:'''<br/>
*YP M2 rc1 had major problems in perl as fallout from the perl upgrade and switch to perl-cross. We’ve therefore built an rc2 based on a more recent master.
*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!
*The python upgrade to 3.7 merged, thanks to AlexK for his hard work on this. It means all of the major components in OE-Core are finally up to date (many minor versions are still adrift).
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*Major util-linux changes have just merged which should hopefully allow easier long term maintenance of this recipe (all binaries now have their own package, this recipe kept being split up)
*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
*Build performance tests on the autobuilder have been improved and builds now have automated result comparisons, e.g.: https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html (from https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101) (Thanks to Markus for a lot of the underlying code/work)
*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.
*Build performance can now compare master to master-next test builds
*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.
*We continue to need help with ptest, both on the tests themselves and on the results reporting. The intent is to have something similar to the build performance pieces above.
*Help us resolve CVE issues: CVE metrics
*The recipe reporting system integration with the layer index is available at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the historical data has now been imported.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*The project is considering moving its mailing list hosting to groups.io, if anyone has any experience of that, positive or negative please let Michael, Nico and Richard know. Note that google has made further significant changes to its mail processing at the detriment to mailing lists: https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.html
*If anyone has feedback about the maintainers/recipe upgrade processes or how to attract new recipe maintainers, please talk to Richard Purdie / Ross Burton


'''Planned Releases for YP 2.7:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7 M2 is built and in QA.
*WDD 2772 (last week 2752) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.7 M2 Release Target is Feb. 1, 2019
*OE-Core/Poky Patch Metrics
*YP 2.7 M3 Cutoff is Feb. 25, 2019
**Total patches found: 1121 (last week 1127)
*YP 2.7 M3 Release Target is Mar. 8, 2019
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 2.7 M4 Release Target is Apr. 26, 2019


'''Planned upcoming dot releases:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*YP 5.1 M1 Build date 2024-05-20
*YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*YP 5.1 M1 Release date 2024-05-31
*YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.
*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


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2356 (last week 2393) (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: 1572 (last week 1583)
*YP 4.0.19 Release date 2024-06-14
**Patches in the Pending State: 678 (43%) [last week 677 (43%)]
*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


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>


== 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]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"