Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
Line 1: Line 1:
== Yocto Project Status 28 July 2026 ==
== Yocto Project Status 4 August 2026 ==
Current Dev Position: YP 6.1 M3<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<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 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 6th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 4th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 6th Aug. 10am GMT and Monday 10th 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 5.0.19 has been released
*YP 6.1 M2 is due for release
*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:
*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
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
**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.
     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.
*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
*Some class cleanups were merged which did require tweaks to some metadata:
**https://lore.kernel.org/openembedded-core/20260802102854.3952760-1-richard.purdie@linuxfoundation.org/
**See the “The series does break some things, notably” section
*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 29: Line 31:
**‘WITH’ license exceptions are now supported
**‘WITH’ license exceptions are now supported
Big thanks to 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!
*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 and we’re trying to catch up with AUH updates.
*We continue to work on the backlog of patches which has slightly reduced.
*Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.
*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.
*Rust is now using a shared work directory which reduces disk usage significantly.
*Remaining intermittent build failures  of concern:
*There have been further important fixes in pseudo which were included in the latest upgrade.
**other qemu ‘hang’ type issues on ARM
*The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**intermittent ptest failures in many recipes


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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2694 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1021 (last week 1019)
**Total patches found: 1029 (last week 1021)
**Patches in the Pending State: 141 (14%) [last week 144 (14%)]
**Patches in the Pending State: 141 (14%) [last week 141 (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: out of QA.
*6.1 M2: due for release
**Release Date: w/c 2026-08-03
**Release Date: w/c 2026-08-03
*6.1 M3:
*6.1 M3:
Line 65: Line 64:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.19 due to release
*YP 6.0.3 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
**Release Date w/c 2026-08-24
*YP 5.0.20
*YP 5.0.20

Latest revision as of 14:47, 4 August 2026

Yocto Project Status 4 August 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:

   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.
  • 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
  • Some class cleanups were merged which did require tweaks to some metadata:
  • 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!

  • We continue to work on the backlog of patches which has slightly reduced and we’re trying to catch up with AUH updates.
  • Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.
  • Rust is now using a shared work directory which reduces disk usage significantly.
  • There have been further important fixes in pseudo which were included in the latest upgrade.
  • The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2: due for release
    • 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 6.0.3 due to release
    • 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=86859"