Weekly Status: Difference between revisions

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


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 23th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Jan. 30th 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. 21th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Jan. 28th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Feb. 11th 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/>
*‘You can quickly test a change to a recipe on a target by rebuilding it alone, then rsyncing pieces of WORKDIR/image/ or WORKDIR/packages-split/PACKAGENAME/ rather than rebuilding the image (bit of a hack but effective).
*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)
*(anyone with tips they’d like to see here, please send to Stephen or Richard)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today.
*YP 3.1 M2 is in QA but has issues with build reproducibility
*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.
*We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
*Patch merging continues to be making good progress and staying roughly up to date.
*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).
*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’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).
*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 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
*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 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 due to the reproducibility issues in particular.
*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.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Proposed YP 3.1 Milestone Dates'''<br/>
*YP 3.1 M2 build date 1/20/2020
*YP 3.1 M2 release date 1/31/2020
*YP 3.1 M2 release date 1/31/2020
*YP 3.1 M3 build date 2/24/2020
*YP 3.1 M3 build date 2/24/2020
Line 40: Line 38:


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


'''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:59, 28 January 2020

Yocto Project Weekly Status January 28, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M2 in QA - release 1/31/20

Next Team Meetings:

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