From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 915B01387FD for ; Tue, 8 Apr 2014 03:25:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5698CE0B1C; Tue, 8 Apr 2014 03:25:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A81ABE0B1C for ; Tue, 8 Apr 2014 03:25:18 +0000 (UTC) Received: from guppy (guppy.gentoo.osuosl.org [140.211.166.179]) by smtp.gentoo.org (Postfix) with SMTP id C8B7B33FF90; Tue, 8 Apr 2014 03:25:16 +0000 (UTC) Received: by guppy (sSMTP sendmail emulation); Tue, 08 Apr 2014 03:25:15 +0000 Date: Tue, 08 Apr 2014 03:25:15 +0000 From: catalyst@guppy.ia64.dev.gentoo.org To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec 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 Message-Id: <20140408032520.5698CE0B1C@pigeon.gentoo.org> X-Archives-Salt: e1c642e2-bbbd-4a6d-9059-52dcea5e10ee X-Archives-Hash: d93d9e1d3959e2460ed532af00c1159a Catalyst, version 2.0.16 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 pkgcache seedcache snapcache" Autoresuming support enabled. Binary redistribution enabled Package cache support enabled. Seed cache support enabled. Snapshot cache support enabled. Envscript support enabled. Using target: stage1 Building natively for ia64 stage1 root path is /tmp/stage1root Source path set to /var/tmp/catalyst/builds/default/stage3-ia64-latest.tar.bz2 Caching snapshot to /var/tmp/catalyst/snapshot_cache/20140408/ The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-ia64-20140408/ stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/tmp/stage1root Location of the package cache is /var/tmp/catalyst/packages/default/stage1-ia64-20140408/ Checking for processes running in chroot and killing them. Removing AutoResume Points: ... Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-ia64-20140408/ >>> 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-ia64-20140408/ clearing chroot ... Emptying directory /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/ clearing package cache ... purging the pkgcache ... clearing 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-ia64-20140408/ Emptying directory /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/ Starting tar extract from /var/tmp/catalyst/builds/default/stage3-ia64-latest.tar.bz2 to /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/ (This may take some time) ... --- Running action sequence: unpack_snapshot Cleaning up invalid snapshot cache at /var/tmp/catalyst/snapshot_cache/20140408/ (This can take a long time)... Unpacking portage tree (This can take a long time) ... lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20140408/.catalyst_lock' --- Running action sequence: setup_confdir --- 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-ia64-20140408///tmp/stage1root/etc/portage Copying stage1-chroot.sh to ./tmp copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/./tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/./tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-ia64-20140408/ >>> Regenerating /etc/ld.so.cache... emerge --quiet --oneshot --nodeps --update sys-apps/portage Performing Global Updates (Could take a couple of minutes if you have a lot of binary packages.) >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/portage-2.2.8-r1 >>> Failed to emerge sys-apps/portage-2.2.8-r1, Log file: >>> '/var/tmp/portage/sys-apps/portage-2.2.8-r1/temp/build.log' * Package: sys-apps/portage-2.2.8-r1 * Repository: gentoo * Maintainer: dev-portage@gentoo.org * Upstream: dev-portage@gentoo.org * USE: build elibc_glibc ia64 ipc kernel_linux python_targets_python2_7 python_targets_python3_3 userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox install: cannot change permissions of '/var/tmp/portage/sys-apps/portage-2.2.8-r1/work': No such file or directory /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * ERROR: sys-apps/portage-2.2.8-r1::gentoo failed (unpack phase): /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * Failed to create dir '/var/tmp/portage/sys-apps/portage-2.2.8-r1/work' /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * Call stack: /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * ebuild.sh, line 714: Called __ebuild_main 'unpack' /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * phase-functions.sh, line 955: Called __dyn_unpack /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * phase-functions.sh, line 240: Called die /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * The specific snippet of code: /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'" /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.8-r1::gentoo'`, /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.8-r1::gentoo'`. /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.2.8-r1/temp/build.log'. /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.8-r1/temp/environment'. /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * Working directory: '/var/tmp/portage/._portage_reinstall_.wPs_fd/pym' /var/tmp/portage/._portage_reinstall_.wPs_fd/bin/isolated-functions.sh: line 246: echo: write error: No space left on device * S: '/var/tmp/portage/sys-apps/portage-2.2.8-r1/work/portage-2.2.8' !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1243, in run_local "run script failed.",env=self.env) File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, 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 1303, in run apply(getattr(self,x)) File "modules/generic_stage_target.py", line 1248, 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-ia64-20140408/.catalyst_lock' Full build log at /tmp/catalyst-auto.32528/log/stage1.log