Yocto Project Status 13 February 2024 (WW07)

Yocto Project Status 13 February 2024 (WW07)

[Stephen K Jolley]

[-- Attachment #1: Type: text/plain, Size: 5771 bytes --]

Current Dev Position: YP 5.0 M3

Next Deadline: 19th February 2024 YP 5.0 M3 build

Next Team Meetings:

   -

   Bug Triage meeting Thursday February 15th at 7:30 am PST (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync Tuesday February 13th at 8 am PST (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   <https://zoom.us/j/990892712>
   -

   Twitch -  See https://www.twitch.tv/theyoctojester


Key Status/Updates:

   -

   YP 4.0.16 was released.
   -

   YP 4.3.3 is in QA.
   -

   We are now a week from feature freeze for 5.0, our next LTS release
   -

   The BBFILE_PRIORITY change is being deferred as unfortunately it causes
   problems with bbappend ordering.
   -

   There have been fixes for python 3.12, recipe upgrades, kernel stable
   version bump and many other fixes and improvements this week.
   -

   The ‘scarthgap’ layer series name has merged to core. Compatibility with
   nanbield will be removed soon so maintainers will need to update their
   layers ASAP for the new release series.
   -

   Patch testing, review and merging is still a little behind due to the
   volume of failures combined with builds needing long buildtimes to do
   rebuilding core components like the compiler or libc.
   -

   Several performance regressions were identified in bitbake for world
   builds and patches have merged to try and improve those.
   -

   LLVMVERSION has been dropped from OE-Core since it doesn’t need it. This
   resolves a long standing issue/conflict with meta-clang but may need fixes
   for other layers that rely upon the variable.
   -

   There have been questions about official RISC-V support in this next
   release, especially since it is an LTS. There is the potential to do this
   since the configurations have been written and are close to working. We’re
   wondering about trial testing this for M3 as a proof of concept. Without
   higher tier project membership support, this will not make it into the LTS
   final release though.


Ways to contribute:

   -

   As people are likely aware, the project has a number of components which
   are either unmaintained, or have people with little to no time trying to
   keep them alive. These components include: devtool, toaster, wic, oeqa,
   autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help
   is welcome in trying to better look after these components!
   -

   There are bugs identified as possible for newcomers to the project:
   https://wiki.yoctoproject.org/wiki/Newcomers
   -

   There are bugs that are currently unassigned for YP 5.0. See:
   https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
   -

   We’d welcome new maintainers for recipes in OE-Core. Please see the list
   at:
   http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
   and discuss with the existing maintainer, or ask on the OE-Core mailing
   list. We will likely move a chunk of these to “Unassigned” soon to help
   facilitate this.
   -

   Help is very much welcome in trying to resolve our autobuilder
   intermittent issues. 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.
   -

   Help us resolve CVE issues: CVE metrics
   <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
   -

   We have a growing number of bugs in bugzilla, any help with them is
   appreciated.
   -

   Regarding bugs, even if you can’t fix a bug, submitting a failing test
   case that can reproduce the issue significantly improves the chances it
   might get fixed.


YP 5.0 Milestone Dates:

   -

   YP 5.0 M3 build date  2024/02/19
   -

   YP 5.0 M3 Release date 2024/03/01
   -

   YP 5.0 M4 build date  2024/04/01
   -

   YP 5.0 M4 Release date 2024/04/30


Upcoming dot releases:

   -

   YP 4.0.16 was released.
   -

   YP 4.3.3 is in QA.
   -

   YP 4.3.3 Release date 2024/02/23
   -

   YP 3.1.32 build date 2024/03/04
   -

   YP 3.1.32 Release date 2024/03/15
   -

   YP 4.0.17 build date 2024/03/11
   -

   YP 4.0.17 Release date 2024/03/22
   -

   YP 4.3.4 build date 2024/03/25
   -

   YP 4.3.4 Release date 2024/04/05
   -

   YP 3.1.33 build date 2024/04/15
   -

   YP 3.1.33 Release date 2024/04/26
   -

   YP 4.0.18 build date 2024/04/22
   -

   YP 4.0.18 Release date 2024/05/03
   -

   YP 4.0.19 build date 2024/06/03
   -

   YP 4.0.19 Release date 2024/06/14


Tracking Metrics:

   -

   WDD 2621 (last week 2574) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1147 (last week 1149)
      -

      Patches in the Pending State: 250 (22%) [last week 249 (22%)]
      -

   https://autobuilder.yocto.io/pub/non-release/patchmetrics/


The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(    *Cell*:                (208) 244-4460

* *Email*:                 *s
<stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com <jolley.yp.pm@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 40820 bytes --]

Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Richard Purdie]

On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
>  * We are now a week from feature freeze for 5.0, our next LTS
> release

For better or worse but probably not entirely surprisingly, there are
quite a few things that we may want to try and fit in. I've listed them
just so everyone knows what is on the list:

* genericarm64 machine
* add qemuriscv64 tests to the autobuilder, for M3 only
* devtool changes to use git notes
* hashserve improvements
* pending changes in master-next where review is still being worked
* change to rust test suite logging
* devtool IDE changes

Also things which are worrying:

* Rust upgrade blocked by reproducibility issues
* musl upgrade blocked by large number of unsubmitted pending patches
* nativesdk-systemd usage broken by usrmerge requirement (we're not 
  changing the SDK layout days before freeze)

I'm sure there are some things I'm forgetting too.

Please let me know ASAP if there is anything else pending.

The good news is that several problematic issues do seem to be finding
resolutions in the last 48h.

Cheers,

Richard

Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Jose Quaresma]

[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]

Richard Purdie <richard.purdie@linuxfoundation.org> escreveu (sexta,
16/02/2024 à(s) 11:34):

> On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
> >  * We are now a week from feature freeze for 5.0, our next LTS
> > release
>
> For better or worse but probably not entirely surprisingly, there are
> quite a few things that we may want to try and fit in. I've listed them
> just so everyone knows what is on the list:
>
> * genericarm64 machine
> * add qemuriscv64 tests to the autobuilder, for M3 only
> * devtool changes to use git notes
> * hashserve improvements
> * pending changes in master-next where review is still being worked
> * change to rust test suite logging
> * devtool IDE changes
>
> Also things which are worrying:
>
> * Rust upgrade blocked by reproducibility issues
> * musl upgrade blocked by large number of unsubmitted pending patches
> * nativesdk-systemd usage broken by usrmerge requirement (we're not
>   changing the SDK layout days before freeze)
>
> I'm sure there are some things I'm forgetting too.
>
> Please let me know ASAP if there is anything else pending.
>

Hi Richard,

I think it would also be important to update the golang toolchain from the
1.20.x
we haven't done it yet the 1.21 and 1.22.
I intend to dedicate some time to 1.21 but I can't promise anything and
there is a
high probability that I won't be able to correct the problems that exist.

Jose


>
> The good news is that several problematic issues do seem to be finding
> resolutions in the last 48h.
>
> Cheers,
>
> Richard
>
>
>
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#195747):
> https://lists.openembedded.org/g/openembedded-core/message/195747
> Mute This Topic: https://lists.openembedded.org/mt/104334498/5052612
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> quaresma.jose@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

-- 
Best regards,

José Quaresma

[-- Attachment #2: Type: text/html, Size: 3373 bytes --]

Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Richard Purdie]

On Fri, 2024-02-16 at 13:12 +0000, Jose Quaresma wrote:
> 
> 
> Richard Purdie <richard.purdie@linuxfoundation.org> escreveu (sexta,
> 16/02/2024 à(s) 11:34):
> > On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
> > >  * We are now a week from feature freeze for 5.0, our next LTS
> > > release
> > 
> > For better or worse but probably not entirely surprisingly, there
> > are
> > quite a few things that we may want to try and fit in. I've listed
> > them
> > just so everyone knows what is on the list:
> > 
> > * genericarm64 machine
> > * add qemuriscv64 tests to the autobuilder, for M3 only
> > * devtool changes to use git notes
> > * hashserve improvements
> > * pending changes in master-next where review is still being worked
> > * change to rust test suite logging
> > * devtool IDE changes
> > 
> > Also things which are worrying:
> > 
> > * Rust upgrade blocked by reproducibility issues
> > * musl upgrade blocked by large number of unsubmitted pending
> > patches
> > * nativesdk-systemd usage broken by usrmerge requirement (we're
> > not 
> >   changing the SDK layout days before freeze)
> > 
> > I'm sure there are some things I'm forgetting too.
> > 
> > Please let me know ASAP if there is anything else pending.
> 
> I think it would also be important to update the golang toolchain
> from the 1.20.x
> we haven't done it yet the 1.21 and 1.22.
> I intend to dedicate some time to 1.21 but I can't promise anything
> and there is a
> high probability that I won't be able to correct the problems that
> exist.

Whilst I agree that would be nice, I have no knowledge in that area, no
available time and nobody else seems to have that either. Not sure what
we can do in that case :(

Cheers,

Richard

Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Alexander Kanavin]

On Fri, 16 Feb 2024 at 14:33, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:

> Whilst I agree that would be nice, I have no knowledge in that area, no
> available time and nobody else seems to have that either. Not sure what
> we can do in that case :(

I'd hope pressure on product-making users to do this update can happen
'naturally' as outdated version becomes a blocker to shipping products
:) The tricky part is to not fall too far behind though.

Alex

Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Alexander Kanavin]

On Fri, 16 Feb 2024 at 12:34, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> I'm sure there are some things I'm forgetting too.
>
> Please let me know ASAP if there is anything else pending.
>
> The good news is that several problematic issues do seem to be finding
> resolutions in the last 48h.

Last week I got the build replicator script and several supplementary
fixes to the point where they do what they're meant to, and they have
tests:
https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/sstate-for-all

Locally it's all working fine, including oe-selftest, but the same
oe-selftest on the AB is failing. Depending on how fast I can fix
this, and how many other issues there are in preparing for LTS, it'll
probably be delayed to after that. I'm ok with that, although I wish
the feature would be a part of that.

Alex