From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stefan Agner <stefan@agner.ch>,
Michael Halstead <mhalstead@linuxfoundation.org>
Cc: ming.liu@toradex.com, rpurdie@linuxfoundation.org,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] uninative: Update to 2.7 release
Date: Fri, 11 Oct 2019 10:00:36 +0100 [thread overview]
Message-ID: <0d5268fcee17db44397f8de81284e400efeb4180.camel@linuxfoundation.org> (raw)
In-Reply-To: <1cc830a84a8b5e58672806f515f0fd0c@agner.ch>
On Fri, 2019-10-11 at 10:26 +0200, Stefan Agner wrote:
> We run several build in parallel using the same downloads folder, it
> seems to me that
> there is a race condition. The history shows the warning several
> times already with
> exit code 127, but in those instances the bulid succeeded
>
> What I don't understand is how the update to 2.7 release could affect
> the behavior
> such that it suddenly leads to issues. Any idea?
We use the bitbake fetcher for uninative so there should be locking,
the same as any other download.
Are these builds in parallel on different machines with a shared
network filesystem for downloads or the same physical machine?
Are you using any special MIRRORS/PREMIRRORS?
FWIW we run many builds on the autobuilder and don't see this. I also
haven't seen any other reports of it.
I'm therefore at a loss as to why the locking would seem to be breaking
for you :(
Cheers,
Richard
next prev parent reply other threads:[~2019-10-11 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 16:47 [PATCH v2] uninative: Update to 2.7 release Michael Halstead
2019-10-07 17:50 ` Khem Raj
2019-10-11 8:26 ` Stefan Agner
2019-10-11 9:00 ` Richard Purdie [this message]
2019-10-11 9:03 ` Stefan Agner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d5268fcee17db44397f8de81284e400efeb4180.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mhalstead@linuxfoundation.org \
--cc=ming.liu@toradex.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpurdie@linuxfoundation.org \
--cc=stefan@agner.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox