Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@×××××××××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec
Date: Tue, 30 Apr 2013 06:41:12
Message-Id: 20130430064109.1C729E086A@pigeon.gentoo.org
tar: gcc-4.6.3/gcc/host-default.c: Cannot open: No space left on device
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/objcp-lang.c: Cannot open: No such file or directory
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/ChangeLog: Cannot open: No such file or directory
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/config-lang.in: Cannot open: No such file or directory
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/lang-specs.h: Cannot open: No such file or directory
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/objcp-decl.c: Cannot open: No such file or directory
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.6.3/gcc/objcp/objcp-decl.h: Cannot open: No such file or directory
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
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * ERROR: sys-devel/gcc-4.6.3 failed (unpack phase):
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * 
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * Call stack:
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 *               ebuild.sh, line   93:  Called src_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 *             environment, line 4195:  Called toolchain_src_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 *             environment, line 4949:  Called gcc_quick_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 *             environment, line 2490:  Called unpack 'gcc-4.6.3.tar.bz2'
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 *   isolated-functions.sh, line   39:  Called die
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * The specific snippet of code:
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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 "$@"
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * 
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'`,
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'`.
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4757: 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.
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * 
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device
 * 
/usr/lib/portage/bin/isolated-functions.sh: line 217: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'.
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'.
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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'
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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 "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, 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 246, 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 4757: 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.
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device
 * 
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device
 * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/gcc-build-logs.tar.bz2 in your bug report
/usr/lib/portage/bin/isolated-functions.sh: line 273: /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 4762: popd: directory stack empty
/usr/lib/portage/bin/misc-functions.sh: line 1245: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device
Traceback (most recent call last):
  File "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, 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 246, 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-2013b 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.20 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.22.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.6.3 merged to /tmp/stage1root/:
 * 
 * LTO support is still experimental and unstable.
 * Any bugs resulting from the use of LTO will not be fixed.
 * 
 * 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 1230, 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 214, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1290, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1235, 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-20130430/.catalyst_lock'



Full build log at /tmp/catalyst-auto.29009/log/stage1.log