From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RkUpy-0007Lc-Uk for garchives@archives.gentoo.org; Tue, 10 Jan 2012 06:05:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2BB6121C09D; Tue, 10 Jan 2012 06:05:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 95D6921C09D for ; Tue, 10 Jan 2012 06:05:32 +0000 (UTC) Received: from i2 (i2.gentoo.osuosl.org [140.211.166.190]) by smtp.gentoo.org (Postfix) with SMTP id B382A1B4009; Tue, 10 Jan 2012 06:05:30 +0000 (UTC) Received: by i2 (sSMTP sendmail emulation); Tue, 10 Jan 2012 06:07:22 +0000 Date: Tue, 10 Jan 2012 06:07: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: <20120110060533.2BB6121C09D@pigeon.gentoo.org> X-Archives-Salt: 01b495dc-99b3-454c-bcb5-e9bdb88dedc5 X-Archives-Hash: 24605ec76375e70340f8f04c84aaf4e4 File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.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.5.3-r1/temp/environment: line 4699: pushd: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build: No such file or directory tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device * /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device * Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/gcc-build-logs.tar.bz2 in your bug report /usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device * /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment: line 4704: popd: directory stack empty /usr/lib/portage/bin/misc-functions.sh: line 978: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device Traceback (most recent call last): File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.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-apps/coreutils-8.7 merged to /tmp/stage1root/: * 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/timezone-data-2011n merged to /tmp/stage1root/: * You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. * Setting /tmp/stage1root/etc/localtime to Factory. * Messages for package net-misc/wget-1.12-r3 merged to /tmp/stage1root/: * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc * Messages for package sys-devel/gcc-4.5.3-r1 merged to /tmp/stage1root/: * 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. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/var/tmp/ccache: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1207, in run_local "run script failed.",env=self.env) File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd raise CatalystError,myexc CatalystError None !!! catalyst: Stage build aborting due to error. /proc is still mounted; performing auto-bind-umount... !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//var/tmp/ccache failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/var/tmp/ccache: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/kerncache: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//var/tmp/ccache !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/kerncache failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/kerncache: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/stage1root/proc: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/kerncache !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/stage1root/proc failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/stage1root/proc: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/usr/portage: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/stage1root/proc !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//usr/portage failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/usr/portage: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/dev: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//usr/portage !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//dev failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/dev: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/proc: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//dev !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//proc failed. !!! catalyst: Killing any pids still running in the chroot Checking for processes running in chroot and killing them. cannot open /etc/mtab.tmp (No space left on device) - mtab not updated umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/proc: not mounted cannot open /etc/mtab.tmp (No space left on device) - mtab not updated !!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//proc Traceback (most recent call last): File "modules/generic_stage_target.py", line 1263, in run apply(getattr(self,x)) File "modules/generic_stage_target.py", line 1212, in run_local raise CatalystError,"Stage build aborting due to error." CatalystError None !!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety. Traceback (most recent call last): File "modules/generic_stage_target.py", line 609, in mount_safety_check self.unbind() File "modules/generic_stage_target.py", line 936, in unbind "Couldn't umount one or more bind-mounts; aborting for safety." CatalystError None !!! catalyst: Unable to auto-unbind /proc Traceback (most recent call last): File "/usr/lib/catalyst/catalyst", line 209, in build_target mytarget.run() File "modules/generic_stage_target.py", line 1265, in run self.mount_safety_check() File "modules/generic_stage_target.py", line 615, in mount_safety_check raise CatalystError, "Unable to auto-unbind "+x CatalystError !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20120110/.catalyst_lock' Full build log at /tmp/catalyst-auto.2430/log/stage1.log