[OE-core] Yocto Project Status WW51’17

[Richard Purdie]

On Fri, 2017-12-22 at 13:23 -0500, Randy MacLeod wrote:
> On 2017-12-18 10:52 AM, Jolley, Stephen K wrote:
> > ·We have identified further intermittent bugs in various releases
> > which 
> > we’re continuing to look into (including gpg memory allocation
> > issues on 
> > pyro, sstate writing races in morty, further occurrences of the
> > inode 
> > count issues with our NAS on the autobuilder).
> If any of the new problems prove to be difficult to debug, please
> reply with the defect ID so that people can read the background
> and perhaps help out in some way.

Thanks, I'm catching up after the holidays. The morty sstate writing
issue was resolved with a backport:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=morty&id=e3ff03599e55fd2abcaa33e29779c388cdbed94e

The gpg issue is:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12022

I've only just realised that I appear to be the one assigned to fix it
:/. So that one remains open and in need of help. We put a single
threaded workaround into master/rocko I think but its slowing down
selftest and really needs a better fix.

> WR used to use a single large NAS for our build cluster 3+ years ago.
> While it worked to first order, there was a background of mysterious
> errors. We switch to local disks and pushing logs/status to
> a centralized git repo and we've been happy with that choice.

In this case we have it working quite well, except for one oddity where
the NFS client free inode counts go a bit crazy. We've decided to stop
checking the free inode count on the NAS for now whilst we continue to
see if we can figure it out which means builds should be working again
and not hitting this. The bug is:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12267

So the gpg one is the one I could use help with.

Cheers,

Richard