From: "Cui, Dexuan" <dexuan.cui@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Some nightly build failures on autobuilder (on commit b9a97e07, namely, "Revert part of the unpack change...")
Date: Mon, 14 Feb 2011 14:52:37 +0800 [thread overview]
Message-ID: <1865303E0DED764181A9D882DEF65FB68630C8DA71@shsmsx502.ccr.corp.intel.com> (raw)
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.
2) on mpc, linux-libc-headers-yocto-2.6.37+git do_install failed:
http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/35/steps/shell_19/logs/stdio
| install: cannot create regular file `/srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/ppc603e-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+343c06b25b221aa7f7019aee83b2d976041fddce_1+343c06b25b221aa7f7019aee83b2d976041fddce-r2/image/boot/devicetree-': No such file or directory
NOTE: package linux-libc-headers-yocto-2.6.37+git-1+343c06b25b221aa7f7019aee83b2d976041fddce
3) ememlow do_rootfs failed:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal/builds/48/steps/shell_9/logs/stdio
| error: Failed dependencies:
| keymaps is needed by task-poky-boot-1.0-r7.emenlow
| base-files is needed by task-poky-boot-1.0-r7.emenlow
| task-base-wifi is needed by task-base-extended-1.0-r69.emenlow
| task-base-bluetooth is needed by task-base-extended-1.0-r69.emenlow
| task-base is needed by task-base-extended-1.0-r69.emenlow
| ...
First I'm trying to reproduce issue 1 now. Mark, do you have any quick thought? :-)
Thanks,
-- Dexuan
next reply other threads:[~2011-02-14 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 6:52 Cui, Dexuan [this message]
2011-02-14 14:11 ` Some nightly build failures on autobuilder (on commit b9a97e07, namely, "Revert part of the unpack change...") 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
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=1865303E0DED764181A9D882DEF65FB68630C8DA71@shsmsx502.ccr.corp.intel.com \
--to=dexuan.cui@intel.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.