[OE-core] Yocto Project Status WW47’17

Randy MacLeod randy.macleod at windriver.com
Tue Nov 21 01:22:05 UTC 2017


On 2017-11-20 10:36 AM, Jolley, Stephen K wrote:
>
> Current Dev Position: YP 2.5 Planning and M1 development
>
> Next Deadline: YP 2.5 M1 cut off of 12/4/17
>
> SWAT team rotation: Juro -> Paul on Nov.17, 2017.
>
> SWAT team rotation: Paul -> Todor on Nov. 24, 2017.
>
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
> Key Status/Updates:
>
> ·There is no real change to the status from last week. We continue to 
> suffer intermittent build failures and are continuing to attempt to 
> debug these.
>
> ·Currently open issues are:
>

Some US-based people may be on holiday later this week so I'm offering
help from the frozen Northland and more importantly from the team in 
Beijing. ;-)

> oqemuppc continues to demonstrate random hangs in boot  in userspace
>

Is we can create a defect for this and point / copy the wiki notes into 
it, that
would help.
    https://wiki.yoctoproject.org/wiki/Qemuppc_Boot_Hangs

I think I had asked Chi to see if he could reproduce this a week or two ago.
When the lack of entropy problem was identified and fix, many people thought
this hang went away as well. Chi can you read the wiki report and see if you
can add anything to them?

> oIssues with 4.13.10 host kernels booting kvm x86 guests on Tumbleweed 
> (Suse) and Fedora 26 (attempting to see if 4.13.12 helps)
>

Robert, can you test Fedora 26. It would help to have a defect open with 
steps to reproduce or
something about the typical workflow/ build time/ day of the week/ phase 
of the moon.

> onfs inode count for the sstate/dldir share appears to break 
> periodically causing the disk monitor to halt the builds (bug 12267)
>

Likely specific to the AB server so no plans to do anything for this bug.

> oa perf build race (bug 12302)
>
  I'll take a look to:
  - see if I can duplicate the bug on a fast build host
  - check upstream to see if the bug is known/fixed
  - see if I can spot a race in the build rules.

> oAn ext filesystem creation/sizing issue (bug 12304)
>

Saul, Are you around this week? Do you have any additional information 
before
leaving for Thanksgiving?

Jackie,
Can you look at the code around the image creation and try to reproduce 
this one?

../Randy

> ·Until we resolve these issues patches will continue to be slow to 
> merge, if at all. This also blocks several core developers from doing 
> any feature work at this point in time (e.g. layer setup tool is on 
> hold, again).
>
> ·We can only continue to stress that unless others step up and help to 
> try and root cause these issues, things will stall with the project.
>
> Planned upcoming dot releases:
>
> YP 2.2.3 is planned and should be out in the next few weeks.
>
> YP 2.3.3 is planned, but date TBD during YP 2.5 planning.
>
> YP 2.4.1 is planned, but date TBD during YP 2.5 planning.
>
> Key YP 2.5 Dates are:
>
> YP 2.5 M1 cut off of 12/4/17
>
> YP 2.5 M1 release of 12/15/17
>
> YP 2.5 M2 cut off of 1/15/18
>
> YP 2.5 M2 release of 1/26/18
>
> YP 2.5 M3 cut off of 2/19/18
>
> YP 2.5 M3 release of 3/2/18
>
> YP 2.5 M4 cut off of 4/2/18
>
> YP 2.5 M4 release of 4/27/18
>
> Tracking Metrics:
>
> WDD 2655 (last week 2640)
>
> (https://wiki.yoctoproject.org/charts/combo.html)
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
>
> [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*
>
> *INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *
>
> (*Work Telephone*: (503) 712-0534
>
> (*Cell*: (208) 244-4460
>
> * *Email*:_stephen.k.jolley at intel.com_
>
>
>

-- 
# Randy MacLeod.  WR Linux
# Wind River an Intel Company

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20171120/2ecdf668/attachment-0002.html>


More information about the Openembedded-core mailing list