Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status January 14, 2020 ==
== Yocto Project Weekly Status January 21, 2020 ==
Current Dev Position: YP 3.1 M2 <br/>
Current Dev Position: YP 3.1 M2 <br/>
Next Deadline: YP 3.1 M2 build date 1/20/2020<br/>
Next Deadline: YP 3.1 M2 build date 1/20/2020<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 16th  at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Jan. 23th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday  Fab. 4th  at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday  Fab. 4th  at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Jan. 21th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Jan. 14th at 8am PDT (https://www.twitch.tv/yocto_project)
*Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Tip of the Week:'''<br/>
'''Tip of the Week:'''<br/>
Line 14: Line 14:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M2 is due to be built next week.
*YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today.
*Patch merging is roughly on track however there are a number of failures identified with key patches (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked on nodistro failure). Most of these issues are making progress over time.
*Python 2 has been finally removed from OE-Core. This was long scheduled and whilst its causing problems for other layers, we really need to resolve those issues now rather than later in the release cycle so it is the right time to finally do this.
*The more worrying aspect is that there are a number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
*Patch merging continues to be making good progress and staying roughly up to date.
*Looking at the build history, “full” images have built cleanly only once in the past month (3 times in the last two months), which is a pretty shocking statistic which summarises the challenges we face there. Most of these are being procrastinated on by the bug owners since we can’t reproduce them at will. We really need help working on these kinds of issues.
*The patch metrics showed significant improvement this week, partly from continuing work done by Alex Kanavin in keeping things up to date but also from the python2 removal.
*We have changed the sstate mirrors to be per release, simply to lower the numbers of files in any given sstate directory.
*Bruce is struggling to get the 5.4 kernel to work on all platforms and any help, particularly with MIPS would be much appreciated. This is blocking the kernel updates at this point.
*We’re starting to see problems as distros enable seccomp in file which then conflicts with our use of pseudo. We need to come up with a better fix but for now, a wrapper script which adds “-S” to the command line for file, injected into PATH is a workaround.
*There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
*There is a separate email about buildtools tarballs continuing toolchains to support building on wider combinations of host distros, please see that for more info if interested in this.
*We continue to struggle to get clean ‘full’ builds.
*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.
*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.


Line 36: Line 40:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2773 (last week 2773) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2758 (last week 2773) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1411 (last week 1400)
**Total patches found: 1357 (last week 1411)
**Patches in the Pending State: 562 (40%) [last week 562 (40%)]
**Patches in the Pending State: 536 (39%) [last week 562 (40%)]


'''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 15:43, 21 January 2020

Yocto Project Weekly Status January 21, 2020

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Tip of the Week:

  • ‘oe-pkgdata-browser’ is a new handy small helper UI added by Ross to visualise the pkgdata held within a build.
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today.
  • Python 2 has been finally removed from OE-Core. This was long scheduled and whilst its causing problems for other layers, we really need to resolve those issues now rather than later in the release cycle so it is the right time to finally do this.
  • Patch merging continues to be making good progress and staying roughly up to date.
  • The patch metrics showed significant improvement this week, partly from continuing work done by Alex Kanavin in keeping things up to date but also from the python2 removal.
  • Bruce is struggling to get the 5.4 kernel to work on all platforms and any help, particularly with MIPS would be much appreciated. This is blocking the kernel updates at this point.
  • We’re starting to see problems as distros enable seccomp in file which then conflicts with our use of pseudo. We need to come up with a better fix but for now, a wrapper script which adds “-S” to the command line for file, injected into PATH is a workaround.
  • There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • There is a separate email about buildtools tarballs continuing toolchains to support building on wider combinations of host distros, please see that for more info if interested in this.
  • We continue to struggle to get clean ‘full’ builds.
  • 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 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • 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:

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=67549"