Weekly Status

Yocto Project Weekly Status February 4, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

• Bug Triage meeting Thursday Feb. 6th at 7:30am PDT (https://zoom.us/j/454367603)
• Monthly Project Meeting Tuesday Fab. 4th at 8am PDT (https://zoom.us/j/990892712)
• Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (https://zoom.us/j/990892712)
• Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)

Tip of the Week:

• The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context).
• Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
• (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

• YP 3.1 M2 is in QA but has issues with build reproducibility
• We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
• There are now serious problems with the build reproducibility test failures on the autobuilder. We’re not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don’t have bugs yet. Help with any of these would be appreciated (or help filing the bugs).
• We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
• We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
• There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
• We continue to struggle to get clean ‘full’ builds due to the reproducibility issues in particular.
• The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

• YP 3.1 M2 should release shortly
• YP 3.1 M3 build date 2/24/2020
• YP 3.1 M3 release date 3/6/2020
• YP 3.1 M4 build date 3/30/2020
• YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

• YP 2.7.3 build date 2/10/2020
• YP 2.7.3 release date 2/21/2020
• YP 3.0.2 build date 2/3/2020
• YP 3.0.2 release date 2/14/2020

Tracking Metrics:

• WDD 2767 (last week 2765) (https://wiki.yoctoproject.org/charts/combo.html)
• Poky Patch Metrics
  • Total patches found: 1368 (last week 1368)
  • Patches in the Pending State: 544 (40%) [last week 545 (40%)]

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

Archives

• 2020 Yocto Project Weekly Status Archive
• 2019 Yocto Project Weekly Status Archive
• 2018 Yocto Project Weekly Status Archive