Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 25th, 2022 ==
== Yocto Project Weekly Status Feb. 1st, 2022 ==
Current Dev Position: YP 3.5 M3<br/>
Current Dev Position: YP 3.5 M3<br/>
Next Deadline: 21th Feb. 2022 YP 3.5 M3 build<br/>
Next Deadline: 21th Feb. 2022 YP 3.5 M3 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 27th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Feb. 3rd  at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Feb. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Monthly Project Meeting Tuesday Feb. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Jan. 25th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Feb. 8th at 8 am 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.5 M2 finally built today after a number of autobuilder build issues and is now in QA
*YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to vacations in Asia the release, if approved, will be made next week.
*Building M2 was fairly painful as various sstate error/warning code paths were exposed in release builds, there were some infrastructure issues, some test reporting bugs and other bugs like that in systemtap on arm and a reproducibility issue, all of which combined to break the release builds in different ways. Hopefully most of these are now addressed or in the process of being fixed/tested.
*YP 3.1.14 is ready for QA but the release will also be delayed until next week.
*Upstream glibc are planning to remove prelink support in 2.35 with patches proposed on their mailing list.https://sourceware.org/pipermail/libc-alpha/2022-January/135565.html The project is unlikely to be able to continue to maintain any prelink support once this happens and we will therefore remove our prelink support before the next LTS unless the situation changes and maintainers step forward.
*Upstream glibc are now planning to remove prelink support in 2.36. I think we will still want to remove prelink from OE-Core before our next release though, particularly as it is an LTS.
*An email proposing inclusive language changes https://lists.openembedded.org/g/openembedded-core/message/160881 for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
*An email proposing inclusive language changes for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
*The debian9 autobuilder issues were hardware related and fixes for the arm systemtap issues are being tested but autobuilder intermittent issues are still at an all time high.
*We are seeing networking issues during image testing on the centos8/stream8 workers, possibly due to recent changes in the distro. Help with debugging this welcome.
*CVE metrics improved for master https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive but work still remains on the various stable branches which have high counts.
*We have also realized there is an issue with hash equivalence where the current mechanism will not account for different headers inside the sysroot added through indirect dependencies (e.g. linux-libc-headers via glibc). This means something like rtcwake in util-linux which uses rtc.h can have differing debug symbols due to differing line numbers yet otherwise be identical. There is a potential fix with downsides in master-next.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
*CVE metrics are still under control for master with pending patches accounted for (thanks Ross!) but work still remains on the various stable branches which have high counts.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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 In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 24: Line 25:


'''YP 3.5 Milestone Dates:'''<br/>
'''YP 3.5 Milestone Dates:'''<br/>
*YP 3.5 M2 is built
*YP 3.5 M2 is out of QA
*YP 3.5 M2 Release date 2022/01/28
*YP 3.5 M3 build date 2022/02/21
*YP 3.5 M3 build date 2022/02/21
*YP 3.5 M3 Release date 2022/03/04
*YP 3.5 M3 Release date 2022/03/04
Line 32: Line 32:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 build date 2022/01/24
*YP 3.1.14 is built
*YP 3.1.14 Release date 2022/02/04
*YP 3.1.14 Release date 2022/02/04
*YP 3.4.2 build date 2022/02/07
*YP 3.4.2 build date 2022/02/07
Line 48: Line 48:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2700 (last week 2675) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2705 (last week 2700) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*Poky Patch Metrics
**Total patches found: 1230 (last week 1229)
**Total patches found: 1236 (last week 1230)
**Patches in the Pending State: 340 (28%) [last week 345 (28%)]
**Patches in the Pending State: 342 (28%) [last week 340 (28%)]


'''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/>

Revision as of 02:36, 1 February 2022

Yocto Project Weekly Status Feb. 1st, 2022

Current Dev Position: YP 3.5 M3
Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to vacations in Asia the release, if approved, will be made next week.
  • YP 3.1.14 is ready for QA but the release will also be delayed until next week.
  • Upstream glibc are now planning to remove prelink support in 2.36. I think we will still want to remove prelink from OE-Core before our next release though, particularly as it is an LTS.
  • An email proposing inclusive language changes for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
  • We are seeing networking issues during image testing on the centos8/stream8 workers, possibly due to recent changes in the distro. Help with debugging this welcome.
  • We have also realized there is an issue with hash equivalence where the current mechanism will not account for different headers inside the sysroot added through indirect dependencies (e.g. linux-libc-headers via glibc). This means something like rtcwake in util-linux which uses rtc.h can have differing debug symbols due to differing line numbers yet otherwise be identical. There is a potential fix with downsides in master-next.
  • CVE metrics are still under control for master with pending patches accounted for (thanks Ross!) but work still remains on the various stable branches which have high counts.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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 In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M2 is out of QA
  • YP 3.5 M3 build date 2022/02/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  • YP 3.1.14 is built
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.3.5 build date 2022/02/14
  • YP 3.3.5 Release date 2022/02/25
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives