[gentoo-releng-autobuilds] [s390-auto] Catalyst fatal build error - stage1.spec

["root" <vapier@gentoo.org>]

Catalyst, version 2.0.18
Copyright 2003-2008 Gentoo Foundation
Copyright 2008-2012 various authors
Distributed under the GNU General Public License version 2.1

Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume bindist kerncache pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage1
Building natively for s390
stage1 root path is /tmp/stage1root
Source path set to /var/tmp/catalyst/builds/default/stage3-s390-latest.tar.bz2
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20161124/
The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161124/
stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390-20161124/tmp/stage1root
Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390-20161124/
Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390-20161124/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161124/
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 
clearing autoresume ...
Removing AutoResume Points: ...
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161124/
clearing chroot ...
Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161124/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
purging the kerncache ...
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to untar...
No Valid Resume point detected, cleaning up...
Removing AutoResume Points: ...
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161124/
Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161124/

Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390-latest.tar.bz2
to /var/tmp/catalyst/tmp/default/stage1-s390-20161124/ (This may take some time) ...

tar: SELinux support is not available
--- Running action sequence: unpack_snapshot
Cleaning up invalid snapshot cache at 
	/var/tmp/catalyst/snapshot_cache/20161124/ (This can take a long time)...
Unpacking portage tree (This can take a long time) ...
tar: SELinux support is not available
lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20161124/.catalyst_lock'
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- Running action sequence: portage_overlay
--- Running action sequence: base_dirs
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...

Warning!!!!
	Overriding certain env variables may cause catastrophic failure.
	If your build fails look here first as the possible problem.
	Catalyst assumes you know what you are doing when setting
		these variables.
	Catalyst Maintainers use VERY minimal envscripts if used at all
	You have been warned

--- Running action sequence: setup_environment
--- Running action sequence: run_local
copying make.conf to /var/tmp/catalyst/tmp/default/stage1-s390-20161124///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161124//tmp
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161124//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390-20161124/
>>> Regenerating /etc/ld.so.cache...
Adding USE=' build' to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)



The following packages are causing rebuilds:

  (sys-libs/ncurses-6.0-r1:0/6::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (sys-apps/less-481:0/0::gentoo, ebuild scheduled for merge)
    (sys-apps/util-linux-2.26.2:0/0::gentoo, ebuild scheduled for merge)
    (app-editors/nano-2.5.3:0/0::gentoo, ebuild scheduled for merge)
    (sys-devel/gettext-0.19.7:0/0::gentoo, ebuild scheduled for merge)
    (sys-apps/openrc-0.19.1:0/0::gentoo, ebuild scheduled for merge)
>>> Verifying ebuild manifests
>>> Emerging (1 of 9) sys-libs/ncurses-6.0-r1::gentoo
>>> Installing (1 of 9) sys-libs/ncurses-6.0-r1::gentoo
>>> Emerging (2 of 9) sys-process/runit-2.1.1-r1::gentoo
>>> Failed to emerge sys-process/runit-2.1.1-r1

 * Messages for package sys-libs/ncurses-6.0-r1:

 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package sys-process/runit-2.1.1-r1:


!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1244, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build aborting due to error.

Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1249, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage1
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390-20161124/.catalyst_lock'
Command exited with non-zero status 1
377.47user 139.50system 6:00.93elapsed 143%CPU (0avgtext+0avgdata 192608maxresident)k
0inputs+0outputs (663major+31736418minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20161124.yPO6Zj/log/stage1.log