Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
Line 1: Line 1:
== Yocto Project Status 21 July 2026 ==
== Yocto Project Status 28 July 2026 ==
Current Dev Position: YP 6.1 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 6.0.2 has been released
*YP 5.0.19 has been released
*YP 5.0.19 is due to release
*YP 6.1 M2 is out of QA and under review
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*Progress has been made with some of the AB-INT issues:
**We identified a kernel issue likely causing the arm psplash boot hangs
**The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
**Several pseudo issues were patched in a recent update
**One infrastructure issue on a worker was corrected
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
    We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Some invasive LICENSE changes have merged into master:
*Some invasive LICENSE changes have merged into master:
**We now require the LICENSE field to match SPDX identifiers.  
**We now require the LICENSE field to match SPDX identifiers.  
Line 20: Line 28:
**CLOSED is no longer a valid value.  
**CLOSED is no longer a valid value.  
**‘WITH’ license exceptions are now supported
**‘WITH’ license exceptions are now supported
Big thanks for Joshua for getting us to the point where we can finally clean this up!
Big thanks to Joshua for getting us to the point where we can finally clean this up!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
*We continue to work on the backlog of patches which has slightly reduced.
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
*Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*Remaining intermittent build failures of concern:
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
**other qemu ‘hang’ type issues on ARM
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
**intermittent ptest failures in many recipes
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 44: Line 48:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1019+)
**Total patches found: 1021 (last week 1019)
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
**Patches in the Pending State: 141 (14%) [last week 144 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Upcoming development releases:'''<br/>
'''Upcoming development releases:'''<br/>
*6.1 M2:
*6.1 M2: out of QA.
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
**Release Date: w/c 2026-08-03
*6.1 M3:
*6.1 M3:

Latest revision as of 14:48, 28 July 2026

Yocto Project Status 28 July 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.19 has been released
  • YP 6.1 M2 is out of QA and under review
  • Progress has been made with some of the AB-INT issues:
    • We identified a kernel issue likely causing the arm psplash boot hangs
    • The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
    • Several pseudo issues were patched in a recent update
    • One infrastructure issue on a worker was corrected
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue
   We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
  • Some invasive LICENSE changes have merged into master:
    • We now require the LICENSE field to match SPDX identifiers.
    • The build will issue warnings when this isn’t the case.
    • Non SPDX licenses will need to be of the form LicenseRef-XXX
    • CLOSED is no longer a valid value.
    • ‘WITH’ license exceptions are now supported

Big thanks to Joshua for getting us to the point where we can finally clean this up!

  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
  • We continue to work on the backlog of patches which has slightly reduced.
  • Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2: out of QA.
    • Release Date: w/c 2026-08-03
  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.19 due to release
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

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