From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Some nightly build failures on autobuilder (on commit b9a97e07, namely, "Revert part of the unpack change...")
Date: Tue, 15 Feb 2011 09:13:33 +0000 [thread overview]
Message-ID: <1297761213.4945.166.camel@rex> (raw)
In-Reply-To: <4D5950FB.9020809@windriver.com>
On Mon, 2011-02-14 at 09:57 -0600, Mark Hatle wrote:
> On 2/14/11 12:52 AM, Cui, Dexuan wrote:
> > 1) Building qemumips meta-toolchain-sdk failed:
> > http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/35/steps/shell_26/logs/stdio
> > eglibc's do_package failed:
> > ERROR: Error executing a python function in /srv/home/pokybuild/poky-slave/nightly-external/build/meta/recipes-core/eglibc/eglibc_2.12.bb:
> > CopyFailed: Command tar -cf - -C /srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/mips-poky-linux/eglibc-2.12-r13/sstate-install-package///package -ps . | tar -xf - -C /srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/mips-poky-linux/eglibc-2.12-r13/package failed with return value 2
> >
> > Looks it's related to Mark's recent commit 3e6d91ec, but what's odd is: qemumips failed here while qemux86 and qemuarm are ok... BTW: MACHINE routerstationpro and atom-pc also have the same failure as qemumips.
>
> I've not seen this error. The code in question would be located in
> meta/classes/package.bbclass. There are only a couple of locations in there
> that we switched to the 'tar' method of copying.
>
> Is there any other error messages in the logs besides the one above?
>
> If it truly was error "2", then it means "No such file or directory".
>
> If someone is able to reproduce this, we can figure out if the source or
> destination are missing and how that occurred.
The error is not from package.bbclass, its from a oe.utils.copytree call
in sstate.bbclass and hence from a commit I made in the same spirit as
Mark's changes. What's going wrong I don't know though.
Cheers,
Richard
prev parent reply other threads:[~2011-02-15 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 6:52 Some nightly build failures on autobuilder (on commit b9a97e07, namely, "Revert part of the unpack change...") Cui, Dexuan
2011-02-14 14:11 ` Bruce Ashfield
2011-02-14 15:08 ` Bruce Ashfield
2011-02-14 15:47 ` Cui, Dexuan
2011-02-14 16:03 ` Cui, Dexuan
2011-02-14 15:57 ` Mark Hatle
2011-02-14 16:09 ` Cui, Dexuan
2011-02-15 9:13 ` 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=1297761213.4945.166.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.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 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.