Current Dev Position: YP 3.4 M1
Next Deadline: 7th June 2021 YP 3.4 M1 build
Next Team Meetings:
- YP 3.2.4 was released
- YP 3.3.1 is in QA
- Patch merging to master is continuing and we now have a round of AUH upgrades to process. We’ve tried to merge some of the easier ones as there was autobuilder testing availability. This allows people to concentrate on the areas where there are issues with the automated upgrade and where we most need the help.
- Anuj is unavailable for a few weeks so Richard will be acting as maintainer for hardknott until he returns (assistance welcome).
- An open letter about open source project work was sent to various mailing lists highlighting some of the challenges established project face from a resourcing perspective:
- The multiconfig changes in bitbake continue to cause problems, we still need simpler test cases to reproduce issues rather than huge builds. The existing patches seem to fix some workloads and break others. Richard is trying to fix but trying to fix autobuilder issues and other problems and these are slow builds to debug.
- We saw a significant drop in open CVEs reported by the tooling against master this week (63 down to 18) and hopefully many more of these have resolutions “in flight”. This will allow us to focus on the real issues and filter out the legacy noise.
- SMP was enabled for qemu on arm/x86 and we switched x86 to a more modern cpu/platform
- One source of the OOM issues on the autobuilder appears to be glibc usermode testing going out of control and using up all system memory. We are investigating the best way to mitigate that but it accounts for some of our intermittent issues.
- When OOM issues occur an issue was identified in bitbake’s heartbeat events causing bitbake to hang. Ironically this was being heavily used by the recent autobuilder load debugging code. There is a patch pending to address this.
- A rare sstate manifest corruption bug was tracked down thanks to information from Martin Jansa, a fix has been merged.
- We have enabled more resource control on the autobuilder for xz memory/thread usage as that was contributing to the OOM issues. More investigation is needed into the rpm/deb controls for xz, help there would be appreciated.
- Intermittent autobuilder issues continue to occur and are now at a record high level. 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
We are working to identify the load pattern on the infrastructure that seems to trigger these.
Ways to contribute:
YP 3.4 Milestone Dates:
- YP 3.4 M1 build date 2021/06/07
- YP 3.4 M1 Release date 2021/06/18
- YP 3.4 M2 build date 2021/07/12
- YP 3.4 M2 Release date 2021/07/23
- YP 3.4 M3 build date 2021/08/23
- YP 3.4 M3 Release date 2021/09/03
- YP 3.4 M4 build date 2021/10/04
- YP 3.4 M4 Release date 2021/10/29
Planned upcoming dot releases:
- YP 3.2.4 is in released
- YP 3.3.1 is in QA
- YP 3.3.1 release date 2021/05/28
- YP 3.1.8 build date 2021/05/24
- YP 3.1.8 release date 2021/06/04
- YP 3.1.9 build date 2021/06/21
- YP 3.1.9 release date 2021/07/02
- YP 3.3.2 build date 2021/07/19
- YP 3.3.2 release date 2021/07/30
- YP 3.1.10 build date 2021/07/26
- YP 3.1.10 release date 2021/08/06
- YP 3.1.11 build date 2021/09/13
- YP 3.1.11 release date 2021/9/24
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Stephen K. Jolley
Yocto Project Program Manager
( Cell: (208) 244-4460
* Email: sjolley.yp.pm@...