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 5F0591381F3 for ; Tue, 1 Oct 2013 07:27:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 29078E0B17; Tue, 1 Oct 2013 07:27:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7AB08E0B17 for ; Tue, 1 Oct 2013 07:27:24 +0000 (UTC) Received: from dolphin (i2.gentoo.osuosl.org [140.211.166.190]) by smtp.gentoo.org (Postfix) with SMTP id 658BE33EDBF; Tue, 1 Oct 2013 07:27:22 +0000 (UTC) Received: by dolphin (sSMTP sendmail emulation); Tue, 01 Oct 2013 07:27:22 +0000 Date: Tue, 01 Oct 2013 07:27:22 +0000 From: catalyst@dolphin.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: <20131001072725.29078E0B17@pigeon.gentoo.org> X-Archives-Salt: 24ccfab3-6cbc-45af-8315-d97fb88d5ce1 X-Archives-Hash: 318499f65635ec90f35c375bebf509f2 tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device tar: gcc-4.6.3/gcc/objcp/Make-lang.in: Cannot open: No such file or directory tar: gcc-4.6.3/gcc/cppdefault.h: Cannot open: No space left on device tar: gcc-4.6.3/gcc/gimple-iterator.c: Cannot open: No space left on device tar: gcc-4.6.3/gcc/tree-into-ssa.c: Cannot open: No space left on device tar: gcc-4.6.3/gcc/tree-chrec.h: Cannot open: No space left on device tar: gcc-4.6.3/ylwrap: Cannot open: No space left on device tar: gcc-4.6.3/MD5SUMS: Cannot open: No space left on device tar: Exiting with failure status due to previous errors /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * ERROR: sys-devel/gcc-4.6.3::gentoo failed (unpack phase): /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * failure unpacking gcc-4.6.3.tar.bz2 /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * Call stack: /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * ebuild.sh, line 93: Called src_unpack /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * environment, line 4291: Called toolchain_src_unpack /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * environment, line 5081: Called gcc_quick_unpack /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * environment, line 2592: Called unpack 'gcc-4.6.3.tar.bz2' /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * phase-helpers.sh, line 345: Called __unpack_tar 'bzip2 -d' /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * phase-helpers.sh, line 315: Called __assert_sigpipe_ok 'failure unpacking gcc-4.6.3.tar.bz2' /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * isolated-functions.sh, line 39: Called die /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * The specific snippet of code: /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3::gentoo'`, /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3::gentoo'`. /var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4882: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-build-logs.tar.bz2 in your bug report /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 190: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'. /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'. /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work' /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device * S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3' Traceback (most recent call last): File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 228, in sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 82, in communicate lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/locks.py", line 105, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/__init__.py", line 259, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' * The ebuild phase 'unpack' 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. /var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4882: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device * /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device * Please include /var/tmp/portage/._portage_reinstall_.y6b3sa/pym/gcc-build-logs.tar.bz2 in your bug report /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device * /var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4887: popd: directory stack empty /var/tmp/portage/._portage_reinstall_.y6b3sa/bin/misc-functions.sh: line 1246: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device Traceback (most recent call last): File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 228, in sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 82, in communicate lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/locks.py", line 105, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/__init__.py", line 259, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' * The ebuild phase 'die_hooks' 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-libs/timezone-data-2013d: * You do not have TIMEZONE set in /etc/timezone. * Skipping auto-update of /etc/localtime. * Messages for package app-portage/portage-utils-0.30: * /etc/portage/postsync.d/q-reinitialize has been installed for convenience * If you wish for it to be automatically run at the end of every --sync: * # chmod +x /etc/portage/postsync.d/q-reinitialize * Normally this should only take a few seconds to run but file systems * such as ext3 can take a lot longer. To disable, simply do: * # chmod -x /etc/portage/postsync.d/q-reinitialize * Messages for package sys-apps/util-linux-2.22.2: * The agetty util now clears the terminal by default. You * might want to add --noclear to your /etc/inittab lines. * Messages for package sys-fs/e2fsprogs-1.42.7: * No /etc/mtab file, creating one temporarily * Messages for package sys-apps/less-457: * lesspipe offers colorization options. Run 'lesspipe -h' for info. * Messages for package sys-apps/coreutils-8.20: * Make sure you run 'hash -r' in your active shells. * You should also re-source your shell settings for LS_COLORS * changes, such as: source /etc/profile * Messages for package sys-libs/glibc-2.15-r3: * Defaulting /etc/host.conf:multi to on * Generating all locales; edit /etc/locale.gen to save time/space * Messages for package sys-devel/gcc-4.6.3: * The ebuild phase 'unpack' 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. !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1235, 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 226, in build_target mytarget.run() File "modules/generic_stage_target.py", line 1295, in run apply(getattr(self,x)) File "modules/generic_stage_target.py", line 1240, 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-20131001/.catalyst_lock' Full build log at /tmp/catalyst-auto.25424/log/stage1.log