Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] runqueue.py: check whether multiple versions of the same PN are due to be built
Date: Mon, 09 Sep 2013 16:29:49 +0100	[thread overview]
Message-ID: <1378740589.3484.123.camel@ted> (raw)
In-Reply-To: <38a257cf48a0e83f75352c5f3eff36c305b48d09.1378129369.git.liezhi.yang@windriver.com>

On Mon, 2013-09-02 at 09:47 -0400, Robert Yang wrote:
> There would be an race issue if we:
> 
> $ bitbake make-3.81 make-3.82
> 
> This because they are being built at the same time which would cause
> unexpected problems, for example:
> 
> [snip]
> ERROR: Package already staged (/path/to/tmp/sstate-control/manifest-qemux86-make.populate-sysroot)?!
> ERROR: Function failed: sstate_task_postfunc
> [snip]
> 
> Or there would be python's strack trace such as:
> 
> [snip]
>  *** 0004:    mfile = open(manifest)
>      0005:    entries = mfile.readlines()
>      0006:    mfile.close()
>      0007:
>      0008:    for entry in entries:
> Exception: IOError: [Errno 2] No such file or directory: xxx
> [snip]
> 
> [YOCTO #5094]
> 
> I think that we can quite earlier to fix the problem.
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>

I've merged this although I did move the code and change the error
message wording a little so the output is less confusing to the user.

Cheers,

Richard



      reply	other threads:[~2013-09-09 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 13:47 [PATCH 0/1] check whether multiple versions of the same PN are due Robert Yang
2013-09-02 13:47 ` [PATCH 1/1] runqueue.py: check whether multiple versions of the same PN are due to be built Robert Yang
2013-09-09 15:29   ` Richard Purdie [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=1378740589.3484.123.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox