Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 10: Line 10:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.5 M1 and YP 3.1.13 were released.
*YP 3.5 M2 is due to build next week
*We have two weeks before the 3.5 M2 build.
*The autobuilder updates have now mostly stabilized and we are potentially seeing a reduction in intermittent failures.
*The autobuilder has undergone significant changes. There are some not unexpected  issues with the new distros now in use there such as python 3.12 deprecations which trigger warnings on Fedora 35. One of the workers does appear to have what is potentially a hardware issue and not all the workers have migrated to SSDs yet (about 50% so far) so there will be some further disruption as this takes place.
*On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. A second patchset has been proposed for discussion where tasks using the network would need to be explicitly marked as such.
*On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. There is a proof of concept patchset for the opt-out basis and some good arguments for and against the opt-in approach.
*The openssl and webkit reproducibility issues have been fixed.
*The new year triggered some reproducible build failures in openssl and webkit due to changing copyright years in the source files, which is a sign of how detailed our reproducibility tests are.
*We have also fixed the reproducibility issues with rust-llvm and golang. With ruby docs disabled, this means we have no reproducibility patch exclusions in OE-Core, thanks Alex Kanavin!
*There is a patchset implementing reproducibility for go which is a welcome improvement and much less invasive than previous approaches.
*The “oldest kernel” setting used for qemu which is architecture specific is causing issues for allarch packages but the various patches to fix it have also caused other issues and highlighted gaps in our sstate hash tests. There are hopefully now patches ready to merge to fix these issues and the gaps in testing.
*CVE issues against master have risen from 7 to 17 so help in addressing those issues would be very welcome.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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


Revision as of 15:38, 11 January 2022

Yocto Project Weekly Status Jan. 11th, 2022

Current Dev Position: YP 3.5 M2
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M2 is due to build next week
  • The autobuilder updates have now mostly stabilized and we are potentially seeing a reduction in intermittent failures.
  • On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. A second patchset has been proposed for discussion where tasks using the network would need to be explicitly marked as such.
  • The openssl and webkit reproducibility issues have been fixed.
  • We have also fixed the reproducibility issues with rust-llvm and golang. With ruby docs disabled, this means we have no reproducibility patch exclusions in OE-Core, thanks Alex Kanavin!
  • The “oldest kernel” setting used for qemu which is architecture specific is causing issues for allarch packages but the various patches to fix it have also caused other issues and highlighted gaps in our sstate hash tests. There are hopefully now patches ready to merge to fix these issues and the gaps in testing.
  • CVE issues against master have risen from 7 to 17 so help in addressing those issues would be very welcome.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M2 build date 2022/01/17
  • YP 3.5 M2 Release date 2022/01/28
  • YP 3.5 M3 build date 2022/02/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  • YP 3.1.14 build date 2022/01/24
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.3.5 build date 2022/02/14
  • YP 3.3.5 Release date 2022/02/25
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

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