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
Date: Tue, 06 Nov 2012 06:22:11 +0000 [thread overview]
Message-ID: <20121106061856.03AECE05D5@pigeon.gentoo.org> (raw)
File "/usr/lib/portage/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main
return ebuild_ipc.communicate(args)
File "/usr/lib/portage/bin/ebuild-ipc.py", line 71, in communicate
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
File "/usr/lib/portage/pym/portage/__init__.py", line 230, 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-r2/.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-r2/temp/environment: line 4624: pushd: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/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 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device
*
/usr/lib/portage/bin/isolated-functions.sh: line 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device
* Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r2/gcc-build-logs.tar.bz2 in your bug report
/usr/lib/portage/bin/isolated-functions.sh: line 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device
*
/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment: line 4629: popd: directory stack empty
/usr/lib/portage/bin/misc-functions.sh: line 1231: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/.die_hooks: No space left on device
Traceback (most recent call last):
File "/usr/lib/portage/bin/ebuild-ipc.py", line 299, in <module>
sys.exit(ebuild_ipc_main(sys.argv[1:]))
File "/usr/lib/portage/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main
return ebuild_ipc.communicate(args)
File "/usr/lib/portage/bin/ebuild-ipc.py", line 71, in communicate
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
File "/usr/lib/portage/pym/portage/__init__.py", line 230, 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-r2/.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-2012f 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 sys-apps/coreutils-8.16 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-apps/util-linux-2.21.2 merged to /tmp/stage1root/:
* The agetty util now clears the terminal by default. You
* might want to add --noclear to your /etc/inittab lines.
* Messages for package sys-libs/glibc-2.15-r3 merged to /tmp/stage1root/:
* Defaulting /etc/host.conf:multi to on
* Messages for package sys-devel/gcc-4.5.3-r2 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
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106/tmp/kerncache: 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 1199, 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-20121106//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-20121106/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-20121106/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-20121106//tmp/kerncache
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//tmp/stage1root/proc
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//usr/portage
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//dev
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106//proc
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1259, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1204, 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 614, in mount_safety_check
self.unbind()
File "modules/generic_stage_target.py", line 940, 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 208, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1261, in run
self.mount_safety_check()
File "modules/generic_stage_target.py", line 620, 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-20121106/.catalyst_lock'
Full build log at /catalyst-auto.6180/log/stage1.log
next reply other threads:[~2012-11-06 6:18 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 6:22 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-13 3:35 [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec catalyst
2020-05-15 4:08 catalyst
2020-05-14 3:46 catalyst
2020-05-13 3:26 catalyst
2020-04-27 3:43 catalyst
2019-10-06 20:06 catalyst
2019-10-04 20:03 catalyst
2019-09-27 3:11 catalyst
2019-09-26 3:12 catalyst
2019-09-25 3:12 catalyst
2019-09-24 3:11 catalyst
2019-09-23 3:11 catalyst
2019-09-22 3:14 catalyst
2018-03-15 3:20 catalyst
2018-01-31 3:16 catalyst
2018-01-26 8:13 catalyst
2016-01-19 4:21 catalyst
2015-12-22 5:10 catalyst
2015-12-15 5:04 catalyst
2015-12-08 5:04 catalyst
2015-12-01 5:04 catalyst
2015-03-24 4:56 catalyst
2015-03-17 3:38 catalyst
2015-02-03 4:58 catalyst
2015-01-27 5:06 catalyst
2015-01-20 5:00 catalyst
2014-04-08 3:25 catalyst
2014-01-28 3:44 catalyst
2014-01-21 3:48 catalyst
2014-01-14 19:06 catalyst
2014-01-07 18:19 catalyst
2013-12-31 18:21 catalyst
2013-10-08 3:43 catalyst
2013-10-01 7:27 catalyst
2013-08-20 9:07 catalyst
2013-06-25 3:46 catalyst
2013-04-30 6:47 catalyst
2013-04-02 7:16 catalyst
2013-03-05 7:02 catalyst
2013-02-19 3:26 catalyst
2012-09-11 6:14 catalyst
2012-06-19 3:38 catalyst
2012-05-08 6:29 catalyst
2012-05-01 5:13 catalyst
2012-04-24 3:53 catalyst
2012-04-17 3:34 catalyst
2012-04-10 3:34 catalyst
2012-01-10 6:07 catalyst
2011-11-15 6:18 catalyst
2011-10-11 6:41 catalyst
2011-08-09 3:29 catalyst
2011-08-02 3:28 catalyst
2011-07-26 3:28 catalyst
2011-06-07 6:02 catalyst
2011-04-12 3:45 catalyst
2011-02-01 3:20 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121106061856.03AECE05D5@pigeon.gentoo.org \
--to=catalyst@dolphin.ia64.dev.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox