Hi
I am also hitting this wall. Any reason why the original patches could
not be merged?
On Fri, Nov 29, 2019 at 5:49 PM Martin Jansa wrote:
>
> On Wed, Aug 30, 2017 at 9:54 AM Martin Jansa wrote:
>>
>> I agree with this patchset and it would be OK with IGNORE_SETSCENE_ERRORS
>> conditional as
On Wed, Aug 30, 2017 at 9:54 AM Martin Jansa wrote:
> I agree with this patchset and it would be OK with IGNORE_SETSCENE_ERRORS
> conditional as well.
>
> We're also sometimes seeing these errors, sometime anticipated when
> cleaning shared sstate-cache on NFS server sometimes unexpected when NFS
> -Original Message-
> From: Andre McCurdy [mailto:armccu...@gmail.com]
> Sent: den 30 augusti 2017 00:04
> To: Peter Kjellerstedt
> Cc: OE Core mailing list
> Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
> errors
>
> On Tue, Aug
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: den 30 augusti 2017 10:03
> To: Peter Kjellerstedt ; Andre McCurdy
>
> Cc: OE Core mailing list
> Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
On Wed, 2017-08-30 at 06:44 +, Peter Kjellerstedt wrote:
> > I have left this code as an error deliberately as this kind of
> > thing should not happen and if it does, there is really something
> > wrong which you need to figure out. It means that at one point
> > bitbake thinks the sstate is p
; > Sent: den 29 augusti 2017 23:50
> > To: Peter Kjellerstedt ; Andre McCurdy
> >
> > Cc: OE Core mailing list
> > Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
> > errors
> >
> > On Tue, 2017-08-29 at 20:59 +, Peter Kjellerst
ling list
> Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
> errors
>
> On Tue, 2017-08-29 at 20:59 +, Peter Kjellerstedt wrote:
> > > -Original Message-
> > > From: Andre McCurdy [mailto:armccu...@gmail.com]
> > > Sent: d
On Tue, Aug 29, 2017 at 1:59 PM, Peter Kjellerstedt
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
On Tue, 2017-08-29 at 20:59 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: Andre McCurdy [mailto:armccu...@gmail.com]
> > Sent: den 29 augusti 2017 22:38
> > To: Peter Kjellerstedt
> > Cc: OE Core mailing list
> > Subject: Re: [OE-co
> -Original Message-
> From: Andre McCurdy [mailto:armccu...@gmail.com]
> Sent: den 29 augusti 2017 22:38
> To: Peter Kjellerstedt
> Cc: OE Core mailing list
> Subject: Re: [OE-core] [PATCH 0/2] Avoid build failures due to setscene
> errors
>
> On Tue, Aug
On Tue, Aug 29, 2017 at 1:00 PM, Peter Kjellerstedt
wrote:
> Occasionally, we see errors on our autobuilders where a setscene task
> fails to retrieve a file from our global sstate cache. It typically
> looks something like this:
>
> WARNING: zip-3.0-r2 do_populate_sysroot_setscene: Failed to fetc
Occasionally, we see errors on our autobuilders where a setscene task
fails to retrieve a file from our global sstate cache. It typically
looks something like this:
WARNING: zip-3.0-r2 do_populate_sysroot_setscene: Failed to fetch URL
file://66/sstate:zip:core2-64-poky-linux:3.0:r2:core2-64:3:\
66
12 matches
Mail list logo
