On Tue, May 7, 2013 at 5:28 PM, Greg Freemyer
On Tue, May 7, 2013 at 10:40 AM, Dinar Valeev
wrote: On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier
wrote: Hi,
since some weeks ppc build fail very often with something like -------- Waiting for device /dev/vda to appear: ok fsck from util-linux 2.21.2 fsck: fsck.ext4: not found fsck: error 2 while executing fsck.ext4 for /dev/vda fsck failed. Mounting root device read-only. Mounting root /dev/vda mount -o ro,defaults -t ext4 /dev/vda /root run-init: /.build/build: Exec format error Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 That problem I'm not aware of.
Do you remember where it happens? We have some memory issues, with the new build machines. Like Invalid pointer errors or Inappropriate ioctl.
I get PPC build failure notifications on occasion recently.
When I look to see what status is, it is typically "blocked" and binaries are available from previous builds. Then a day or two later I check again and the build log shows success.
Here's a hermes emails from 3 days ago, trimmed to only have PPC failures. Some of these may be real. I've quit chasing down PPC failures since they seem to be mostly false alarms:
Digest TOC: [ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of security/bulk_extractor openSUSE_Factory_PowerPC/ppc [ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of security/sleuthkit openSUSE_Factory_PowerPC/ppc <snip> [ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc [ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of security/mac-robber openSUSE_Factory_PowerPC/ppc
[ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of security/bulk_extractor openSUSE_Factory_PowerPC/ppc
Package bulk_extractor (version 1.3.1-25.6) of project security failed to build for openSUSE_Factory_PowerPC / ppc.
Review the build log: osc remotebuildlog security bulk_extractor openSUSE_Factory_PowerPC ppc | less
Check out the package for editing: osc checkout security bulk_extractor
[ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of security/sleuthkit openSUSE_Factory_PowerPC/ppc
Package sleuthkit (version 4.0.2-31.10) of project security failed to build for openSUSE_Factory_PowerPC / ppc.
Review the build log: osc remotebuildlog security sleuthkit openSUSE_Factory_PowerPC ppc | less
Check out the package for editing: osc checkout security sleuthkit
<snip>
[ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc
Package libregf (version 0~20130319-11.2) of project devel:libraries:c_c++ failed to build for openSUSE_Factory_ppc / ppc.
Review the build log: osc remotebuildlog devel:libraries:c_c++ libregf openSUSE_Factory_ppc ppc | less
Check out the package for editing: osc checkout devel:libraries:c_c++ libregf
[ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of security/mac-robber openSUSE_Factory_PowerPC/ppc
Package mac-robber (version 1.02-11.9) of project security failed to build for openSUSE_Factory_PowerPC / ppc.
Review the build log: osc remotebuildlog security mac-robber openSUSE_Factory_PowerPC ppc | less
Check out the package for editing: osc checkout security mac-robber If those packages failing on either build65 or build66, this is a known problem. Triggering rebuild makes package built.
We're trying hard to reproduce such failure locally, so we can fix KVM. But so far this happens only within OBS. No luck with trying to reproduce it locally.
-- Greg
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org