From: Mike Crowe <mac@mcrowe.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] image.py: avoid mkdir race when building multiple images
Date: Thu, 19 Nov 2015 11:50:44 +0000 [thread overview]
Message-ID: <20151119115044.GA5875@mcrowe.com> (raw)
In-Reply-To: <1447932227.12500.121.camel@linuxfoundation.org>
On Thursday 19 November 2015 at 11:23:47 +0000, Richard Purdie wrote:
> On Thu, 2015-11-19 at 11:20 +0000, Mike Crowe wrote:
> > The sysroot directory will already exist so let's just try and make the
> > imgdata directory and cope with the exception thrown if it already
> > exists. This stops the race being fatal.
> How about using bb.utils.mkdirhier() which already does this?
I wasn't aware of that function. It's much simpler. I've updated the patch.
Thanks.
Mike.
prev parent reply other threads:[~2015-11-19 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 11:20 [PATCH 1/2] image.py: avoid mkdir race when building multiple images Mike Crowe
2015-11-19 11:23 ` Richard Purdie
2015-11-19 11:50 ` Mike Crowe [this message]
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=20151119115044.GA5875@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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