From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id EA6AD1395E2 for ; Thu, 17 Nov 2016 08:44:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4E660E07D2; Thu, 17 Nov 2016 08:44:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 227AFE07D2 for ; Thu, 17 Nov 2016 08:44:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id C4DC2341026; Thu, 17 Nov 2016 08:44:28 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-9999 required=5.5 tests=[BAYES_00=-1.9, SHORTCIRCUIT=-100] autolearn=disabled Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pl748wCSd3BD; Thu, 17 Nov 2016 08:44:28 +0000 (UTC) Received: from nightheron.gentoo.org (nightheron.gentoo.org [IPv6:2001:470:1f13:1279:21e:4fff:fe17:d5a1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 3AE90340AC7; Thu, 17 Nov 2016 08:44:28 +0000 (UTC) Received: from lgentoo3 (localhost [IPv6:::1]) by nightheron.gentoo.org (Postfix) with SMTP id E69B42EEDF; Thu, 17 Nov 2016 08:44:25 +0000 (UTC) Received: by lgentoo3 (sSMTP sendmail emulation); Thu, 17 Nov 2016 03:44:25 -0500 From: "root" Date: Thu, 17 Nov 2016 03:44:25 -0500 To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [s390-auto] Catalyst fatal build error - stage1.spec Message-Id: <20161117084425.E69B42EEDF@nightheron.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Reply-To: gentoo-releng-autobuilds@lists.gentoo.org X-Archives-Salt: 7549737a-94ac-4e92-b5e9-cab493a063c6 X-Archives-Hash: 48064853deabda425457aab8c1fd26c5 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/20161117/ The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390-20161117/tmp/stage1root Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390-20161117/ Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390-20161117/ Checking for processes running in chroot and killing them. Removing AutoResume Points: ... Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ >>> 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-20161117/ clearing chroot ... Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ 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-20161117/ Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390-latest.tar.bz2 to /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ (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/20161117/ (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/20161117/.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-20161117///tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161117//tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161117//tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ >>> 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-20161117/.catalyst_lock' Command exited with non-zero status 1 387.35user 151.84system 8:20.46elapsed 107%CPU (0avgtext+0avgdata 193552maxresident)k 0inputs+0outputs (669major+31755264minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20161117.9TEXFc/log/stage1.log