Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(418 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 22, 2021 ==
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 3.4 M2<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 12th July 2021 YP 3.4 M2 build<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday June 24th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday July 6th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 22nd at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.4 M1 has been through QA pending release approval with two QA issues highlighted.
*YP 5.0.17 is due to be released
*YP 3.1.9 is being built ready for QA.
*YP 6.0 M3 is in QA
*Big thanks to Paul Gortmaker for tracking down the cause of an LTP null pointer dereference (and other errors) within the cgroups mount code which was responsible for several of our LTP hangs. The issue was introduced in new code between 5.0 and 5.1 in the kernel and had been present for a while. The fix is now making its way through various kernel trees upstream.
*YP 4.0.35 is queued for QA
*Sadly, the above fix did not resolve the “rcu” autobuilder VM hangs we are seeing occasionally. These are odd in that they affect kvm and non-kvm builds (x86 and arm seen on x86-64 hosts), they pin the VM at 300-400% CPU usage and the VM will respond to pings but no ssh or console output. The rcu dumps from the kernel are likely a symptom that something is wrong rather than the cause and often look incomplete. It is as if some instantaneous host load breaks timers in a way the guest cannot recover or continue execution from. We’re continuing to try and narrow this down but it is proving elusive and progress is slow, any insight anyone may have would be welcome.
*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
There are new manual sections that have recently been added on Reproducible Builds and Yocto Project Compatible.
*Issues with pending work needed:
*We continue to deal with an issue with centos8 kernels having what looks like bad bounds checking on the utimensat_time64 32 bit syscalls where the syscall was backported into a kernel point release. We’re working on reporting it upstream.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*We have a 10th anniversary T-shirt and some other Yocto Project items (hoody, stickers, mugs etc.) now available at https://yoctoproject.org/shop (EU and Americas sources)
**Reports of pseudo errors on Fedora 44 beta related to openat2()
*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.
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
*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.
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
*If you have any final patches for whinlatter, please get these sent to the list ASAP.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*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 a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*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.
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 3.4 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.4 M1 is in review
*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.4 M2 build date 2021/07/12
*OE-Core/Poky Patch Metrics
*YP 3.4 M2 Release date 2021/07/23
**Total patches found: 1072 (last week 1060)
*YP 3.4 M3 build date 2021/08/23
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
*YP 3.4 M3 Release date 2021/09/03
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 3.4 M4 build date 2021/10/04
*YP 3.4 M4 Release date 2021/10/29


'''Planned upcoming dot releases:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.1.9 is being built
*YP 6.0 M3 in QA.
*YP 3.1.9 release date 2021/07/02
*YP 6.0 M4 Build Date 2026-04-13
*YP 3.3.2 build date 2021/07/19
*YP 6.0 M4 Release Date 2026-05-04
*YP 3.3.2 release date 2021/07/30
*YP 3.1.10 build date 2021/07/26
*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 2684 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.17 is in review.
*Poky Patch Metrics  
*YP 4.0.35 is in QA.
**Total patches found: 1272 (last week 1270)
*YP 5.3.4
**Patches in the Pending State: 481 (38%) [last week 484 (38%)]
**Build Date 2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''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 54: Line 61:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[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]]

Revision as of 14:47, 14 April 2026

Yocto Project Status 14 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 M4 Build Date 2026-04-20

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 5.0.17 is due to be released
  • YP 6.0 M3 is in QA
  • YP 4.0.35 is queued for QA
  • We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
  • Issues with pending work needed:
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Reports of pseudo errors on Fedora 44 beta related to openat2()
    • Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
    • Meta-oe cve layer filtering under new tooling (metrics script tweak?)
    • Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
  • There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.

git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.

  • The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
  • We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
  • The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
  • If you have any final patches for whinlatter, please get these sent to the list ASAP.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M3 in QA.
  • YP 6.0 M4 Build Date 2026-04-13
  • YP 6.0 M4 Release Date 2026-05-04

Upcoming dot releases:

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