From: Maxim Uvarov <maxim.uvarov@linaro.org>
To: Paul Barker <pbarker@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] wic: fix images build in parallel
Date: Mon, 13 Jan 2020 16:57:30 +0300 [thread overview]
Message-ID: <CAD8XO3a66v27ohEbrjEC=+XanfD1Fo_zXXo9TaFYSr+C+9+jDQ@mail.gmail.com> (raw)
In-Reply-To: <CAM9ZRVt00houpaZaKirGYgu1w_WRm1yqoio_G-wAgdyyGwuAAg@mail.gmail.com>
On Mon, 13 Jan 2020 at 16:31, Paul Barker <pbarker@konsulko.com> wrote:
>
> On Mon, 13 Jan 2020 at 13:08, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:
> >
> > OE wic plugins create temporary file with the index of the line
> > tmp file name. This causes race in case several builds run in time.
> > Add more entropy as timestamp to remove this race.
>
> How would two wic images to be built in parallel with the same work
> directory? To my understanding an image recipe only supports building
> a single wic image.
>
> Thanks,
> Paul
bitbake image1 image2 image3
all images build .wics and use about the same files, like firmware.
Issue is similar to that:
https://www.yoctoproject.org/pipermail/yocto/2018-June/041373.html
Maxim.
next prev parent reply other threads:[~2020-01-13 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 13:08 [PATCHv2] wic: fix images build in parallel Maxim Uvarov
2020-01-13 13:31 ` Paul Barker
2020-01-13 13:57 ` Maxim Uvarov [this message]
2020-01-13 14:00 ` Paul Barker
2020-01-13 14:11 ` Maxim Uvarov
2020-01-17 10:18 ` Paul Barker
2020-01-17 11:59 ` Maxim Uvarov
2020-01-17 12:17 ` Paul Barker
2020-01-17 12:27 ` Paul Barker
2020-01-17 12:39 ` Maxim Uvarov
2020-01-17 21:26 ` Maxim Uvarov
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='CAD8XO3a66v27ohEbrjEC=+XanfD1Fo_zXXo9TaFYSr+C+9+jDQ@mail.gmail.com' \
--to=maxim.uvarov@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pbarker@konsulko.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.