2022 Yocto Project Weekly Status Archive: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 12: Line 12:
*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.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.
*YP 3.1.14 is ready for QA but the release will also be delayed until next week.
*A new Patchwork is available at https://patchwork.yoctoproject.org/. This new system is running the up to date mainline code and will receive regular updates. The previous unmaintained fork remains up at https://patchwork.openembedded.org/ to preserve history. We are seeking help updating PatchTest to run with the new version. Everyone can now sign up for an account on the new system. Patchwork project maintainers please email mhalstead@linuxfoundation.org to have your access restored.
*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.
*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.
*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.
Line 55: Line 56:
'''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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
== Yocto Project Weekly Status Jan. 25th, 2022 ==
== Yocto Project Weekly Status Jan. 25th, 2022 ==
Current Dev Position: YP 3.5 M3<br/>
Current Dev Position: YP 3.5 M3<br/>

Revision as of 16:09, 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.
  • A new Patchwork is available at https://patchwork.yoctoproject.org/. This new system is running the up to date mainline code and will receive regular updates. The previous unmaintained fork remains up at https://patchwork.openembedded.org/ to preserve history. We are seeking help updating PatchTest to run with the new version. Everyone can now sign up for an account on the new system. Patchwork project maintainers please email mhalstead@linuxfoundation.org to have your access restored.
  • 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

Yocto Project Weekly Status Jan. 25th, 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 finally built today after a number of autobuilder build issues and is now in QA
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M2 is built
  • YP 3.5 M2 Release date 2022/01/28
  • 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 build date 2022/01/24
  • 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

Yocto Project Weekly Status Jan. 18th, 2022

Current Dev Position: YP 3.5 M2
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M2 is due to build this week
  • Work has progressed on inclusive language and an email should be out this week about the proposals for that after discussions amongst the volunteers who stepped up to work on it. Some obsolete variables/code have already been removed as a prelude to this.
  • Patches to switch to setuptools and away from distutils following upstream python’s lead have merered (thanks Tim!). Whilst the issues are resolved for core, work remains on other layers such as meta-oe.
  • The autobuilder does look improved from an intermittent failure perspective but we’re seeing hangs for unknown reasons on debian9 oe-selftest (seems python pthread mutex related) and on ltp on the arm worker. Sadly the open issues are at an all time high.
  • Patches to disable the network outside of do_fetch have merged.
  • Support for improved SPDX info for the kernel has merged (thanks Saul).
  • CVE issues had a bad week with further significant increases for master and stable branches. Some patches have merged to improve master (thanks Ross!).
  • 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M2 build date 2022/01/17
  • YP 3.5 M2 Release date 2022/01/28
  • 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 build date 2022/01/24
  • 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

Yocto Project Weekly Status Jan. 11th, 2022

Current Dev Position: YP 3.5 M2
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M2 is due to build next week
  • The autobuilder updates have now mostly stabilized and we are potentially seeing a reduction in intermittent failures.
  • On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. A second patchset has been proposed for discussion where tasks using the network would need to be explicitly marked as such.
  • The openssl and webkit reproducibility issues have been fixed.
  • We have also fixed the reproducibility issues with rust-llvm and golang. With ruby docs disabled, this means we have no reproducibility patch exclusions in OE-Core, thanks Alex Kanavin!
  • The “oldest kernel” setting used for qemu which is architecture specific is causing issues for allarch packages but the various patches to fix it have also caused other issues and highlighted gaps in our sstate hash tests. There are hopefully now patches ready to merge to fix these issues and the gaps in testing.
  • CVE issues against master have risen from 7 to 17 so help in addressing those issues would be very welcome.
  • 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M2 build date 2022/01/17
  • YP 3.5 M2 Release date 2022/01/28
  • 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 build date 2022/01/24
  • 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

Yocto Project Weekly Status Jan. 4th, 2022

Current Dev Position: YP 3.5 M2
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M1 and YP 3.1.13 were released.
  • We have two weeks before the 3.5 M2 build.
  • The autobuilder has undergone significant changes. There are some not unexpected issues with the new distros now in use there such as python 3.12 deprecations which trigger warnings on Fedora 35. One of the workers does appear to have what is potentially a hardware issue and not all the workers have migrated to SSDs yet (about 50% so far) so there will be some further disruption as this takes place.
  • On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. There is a proof of concept patchset for the opt-out basis and some good arguments for and against the opt-in approach.
  • The new year triggered some reproducible build failures in openssl and webkit due to changing copyright years in the source files, which is a sign of how detailed our reproducibility tests are.
  • There is a patchset implementing reproducibility for go which is a welcome improvement and much less invasive than previous approaches.
  • 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M1 is released
  • YP 3.5 M2 build date 2022/01/17
  • YP 3.5 M2 Release date 2022/01/28
  • 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.13 is released
  • YP 3.1.14 build date 2022/01/24
  • 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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=2022_Yocto_Project_Weekly_Status_Archive&oldid=85121"