Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status February 11, 2020 ==
== Yocto Project Weekly Status February 18, 2020 ==
Current Dev Position: YP 3.1 M3 <br/>
Current Dev Position: YP 3.1 M3 <br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Feb. 13th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Feb. 20th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday  Mar. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday  Mar. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Feb. 18th 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 Mar. 10th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M2 was released
*The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
*We’re now in a much better position with reproducibility issues after around 20 patches merged addressing various problems. Some issues still remain but the bulk of the issues appear to be under control now.
*YP 3.0.2 rc2 is in QA with the report due soon.
*Due to the number and type of fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with the reproducibility fixes (as well as additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for a reasonable set of improvements.
*We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
*YP 3.0.2 should therefore enter QA within the next day or so.
*A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
*Review of newly queued warrior (2.7.3) patches will happen later this week once 3.0.2 is in QA.
*Warrior patches for 2.7.3 are out for review.
*With the new fixes and a small fix to the autobuilder code, we managed the first green “full” build in nearly three months.
*With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
*The incoming patch queue is roughly under control again
*We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues.
*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’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).
*One worrying metric is that the WDD is now on level with the high of 2017 so our worst defect weighting in two years. This is sadly unsurprising and directly correlated to a lack of participation in the triage process and a lack of people working on general bug fixing.
*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 28: Line 27:


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 2.7.3 build date 2/10/2020
*YP 2.7.3 built and in QA
*YP 2.7.3 release date 2/21/2020
*YP 2.7.3 release date 2/21/2020
*YP 3.0.2 build date  2/3/2020
*YP 3.0.2 build date  2/3/2020
Line 34: Line 33:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2728 (last week 2767) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2710 (last week 2728) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1361 (last week 1368)
**Total patches found: 1360 (last week 1361)
**Patches in the Pending State: 547 (40%) [last week 544 (40%)]
**Patches in the Pending State: 546 (40%) [last week 547 (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 16:05, 18 February 2020

Yocto Project Weekly Status February 18, 2020

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

Next Team Meetings:

Key Status/Updates:

  • The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
  • YP 3.0.2 rc2 is in QA with the report due soon.
  • We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
  • A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
  • Warrior patches for 2.7.3 are out for review.
  • With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
  • We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues.
  • 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).
  • 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 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 built and in QA
  • 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=69339"