Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status July 5th, 2022 ==
== Yocto Project Weekly Status July 12th, 2022 ==
Current Dev Position: YP 4.1 M2<br/>
Current Dev Position: YP 4.1 M2<br/>
Next Deadline: 11th July 2022 YP 4.1 M2 Build<br/>
Next Deadline: 11th July 2022 YP 4.1 M2 Build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday July 7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday July 14th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday July 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday July 12th 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/>


*Next week M2 is due to build so if anyone has changes for that milestone, please send ASAP.
*YP 4.1 M2 is due to build this week.
*YP 4.0.2 has been through QA and is likely to be released in the next few days.
*YP 4.0.2 was released.
*A reproducibility issue was identified and raised a question on whether we could enable              an old QA check for these kinds of issues (‘buildpaths’ in insane.bbclass). Some bugs were fixed in the test but is has highlighted several reproducibility issues. Some have been fixed but others remain:
*We have fixes in place for most of the reproducible build issues so will enable the buildpaths QA test by default soon once the remaining tweaks have merged. This will allow much easier visibility into reproducibility issues in people’s builds
**docs issues in lib32-vala, rpm, lib32-gtk-doc, vala, gtk-doc
*meta-gplv2 builds have been dropped from master and the layer will no longer be maintained.
**musl issue in ltp
*An issue has been identified where libstdc++ is broken when built with the gold linker due to patch changes that changed the build process in kirkstone.
**multilib issues in lib32-vala, vala, rpm (may overlap docs)
*Systemd is going to require usrmerge in the future. The proposed patch to require that distro feature will break our autobuilder configuration as things stand so work will be needed to try and adapt to the direction from upstream.
**qemuarm64 kernel-devsrc issue (Bruce looking into)
*Recent changes to package.bbclass for externalsrc handling have broken source and license handling for the kernel, highlighting the need to better tests there. We don’t have a fix as yet.
**meta-virt issues in xen-tools (Christopher looking into)
*There have been further proposed patches around improving the eSDK tooling workflows and around layer setup.
**meta-gplv2 issues in mc, tar
*Work is continuing on the /proc/pressure monitoring code.
**lttng-modules .debug issue on beaglebone, edgerouter, and qemumips
*Fixing these will allow us to enable buildpaths by default which should allow more people to spot reproducibility issues.
*There is a discussion about layer setup tooling in the bitbake-layers discussion on the OE-Core list, input is welcome from those with an interest in this.
*There is also a RFC series about improving the eSDK tooling workflows from Alex Kanavin which may be of interest.
*Code to monitor the /proc/pressure interface has been added and there is a patch to optionally allow bitbake to reduce the number of processes running depending on system load, which it is hoped may help some of our autobuilder intermittent issues (thanks Aryaman and Randy).
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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


Line 41: Line 36:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.2 build date 2022/06/27 - pending TSC approval
*YP 4.0.2 Release date 2022/07/08
*YP 4.0.2 Release date 2022/07/08
*YP 3.1.18 build date 2022/07/18
*YP 3.1.18 build date 2022/07/18
Line 57: Line 51:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2387 (last week 2400) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2397 (last week 2387) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1158 (last week 1151)
**Total patches found: 1155 (last week 1158)
**Patches in the Pending State: 328 (28%) [last week 326 (28%)]
**Patches in the Pending State: 327 (28%) [last week 328 (28%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


Revision as of 14:13, 12 July 2022

Yocto Project Weekly Status July 12th, 2022

Current Dev Position: YP 4.1 M2
Next Deadline: 11th July 2022 YP 4.1 M2 Build

Next Team Meetings:

Key Status/Updates:

  • YP 4.1 M2 is due to build this week.
  • YP 4.0.2 was released.
  • We have fixes in place for most of the reproducible build issues so will enable the buildpaths QA test by default soon once the remaining tweaks have merged. This will allow much easier visibility into reproducibility issues in people’s builds
  • meta-gplv2 builds have been dropped from master and the layer will no longer be maintained.
  • An issue has been identified where libstdc++ is broken when built with the gold linker due to patch changes that changed the build process in kirkstone.
  • Systemd is going to require usrmerge in the future. The proposed patch to require that distro feature will break our autobuilder configuration as things stand so work will be needed to try and adapt to the direction from upstream.
  • Recent changes to package.bbclass for externalsrc handling have broken source and license handling for the kernel, highlighting the need to better tests there. We don’t have a fix as yet.
  • There have been further proposed patches around improving the eSDK tooling workflows and around layer setup.
  • Work is continuing on the /proc/pressure monitoring code.
  • Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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 4.1 Milestone Dates:

  • YP 4.1 M2 build date 2022/07/11
  • YP 4.1 M2 Release date 2022/07/22
  • YP 4.1 M3 build date 2022/08/22
  • YP 4.1 M3 Release date 2022/09/02
  • YP 4.1 M4 build date 2022/10/03
  • YP 4.1 M4 Release date 2022/10/28

Upcoming dot releases:

  • YP 4.0.2 Release date 2022/07/08
  • YP 3.1.18 build date 2022/07/18
  • YP 3.1.18 Release date 2022/07/29
  • YP 4.0.3 build date 2022/08/08
  • YP 4.0.3 Release date 2022/08/19
  • YP 3.1.19 build date 2022/08/29
  • YP 3.1.19 Release date 2022/09/09
  • YP 4.0.4 build date 2022/09/19
  • YP 4.0.4 Release date 2022/09/30
  • YP 3.1.20 build date 2022/10/10
  • YP 3.1.20 Release date 2022/10/21
  • YP 4.0.5 build date 2022/10/31
  • YP 4.0.5 Release date 2022/11/11

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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=85341"