Re: [PATCH 0/2] Avoid build failures due to setscene errors

[Peter Kjellerstedt <peter.kjellerstedt@axis.com>]

> -----Original Message-----
> From: Andre McCurdy [mailto:armccurdy@gmail.com]
> Sent: den 30 augusti 2017 00:04
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
> errors
> 
> On Tue, Aug 29, 2017 at 1:59 PM, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> > We do have a daily job that cleans up the global sstate cache and
> > removes files that have not been accessed in the last ten days, but
> > it seems unlikely that it should remove a file that just happens to
> > be required again, and do it at exactly the time when that task is
> > building.
> 
> I guess you've already confirmed that accessing the sstate files over
> NFS does actually modify atime on the server (and that the filesystem
> on the server really does have atime support enabled, e.g. mounted
> with strictatime rather than relatime etc)?

Well, it is mounted with relatime. However, only updating the access 
time once a day should be ok since we are only concerned with changes 
that have not been accessed in the last ten days.

> If access time isn't being determined reliably and sstate files are
> being removed 10 days after being created then that might make the
> race a little more likely to trigger.

The thing is that the cleaning script runs at 3 am (and takes about 
15 minutes to complete), but we have seen the build problem at times 
when no cleaning is taking place. I am currently leaning more towards 
network glitches as the source of the problem, but that is hard to 
verify.

//Peter