[gentoo-releng-autobuilds] [ia64-auto] Catalyst non-fatal build error - installcd-stage1.spec

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1f-mt-1_49.a

    cp "bin.v2/libs/math/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_math_tr1f-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1f-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1f-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1l-mt-1_49.a

    cp "bin.v2/libs/math/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_math_tr1l-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1l-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_tr1l-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99-mt-1_49.a

    cp "bin.v2/libs/math/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_math_c99-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99f-mt-1_49.a

    cp "bin.v2/libs/math/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_math_c99f-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99f-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99f-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99l-mt-1_49.a

    cp "bin.v2/libs/math/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_math_c99l-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99l-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_math_c99l-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_program_options-mt-1_49.a

    cp "bin.v2/libs/program_options/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_program_options-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_program_options-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_program_options-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a

    cp "bin.v2/libs/random/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_random-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a

    cp "bin.v2/libs/serialization/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_serialization-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a

    cp "bin.v2/libs/serialization/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_wserialization-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a

    cp "bin.v2/libs/signals/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_signals-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a

    cp "bin.v2/libs/test/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_prg_exec_monitor-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a

    cp "bin.v2/libs/test/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_unit_test_framework-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a

    cp "bin.v2/libs/timer/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_timer-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a': No space left on device
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a

    cp "bin.v2/libs/wave/build/gcc-4.6/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_wave-mt-1_49.a"  "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a"

cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a': No space left on device
...failed updating 312 targets...
 * ERROR: dev-libs/boost-1.49.0-r2 failed (install phase):
 *   Installation of Boost libraries failed
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_install
 *   environment, line 5392:  Called installation
 *   environment, line 5361:  Called die
 * The specific snippet of code:
 *           ${BJAM} -q -d+2 gentoorelease --user-config=user-config.jam ${OPTIONS} threading=single,multi ${LINK_OPTS} runtime-link=shared --includedir="${D}usr/include" --libdir="${D}usr/$(get_libdir)" $(use python && echo --python-buildid=${PYTHON_ABI}) install || die "Installation of Boost libraries failed";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/boost-1.49.0-r2'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.49.0-r2'`.
/var/tmp/portage/._portage_reinstall_.zciy5m/bin/isolated-functions.sh: line 217: /var/tmp/portage/dev-libs/boost-1.49.0-r2/.die_hooks: No space left on device
 * The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0'
 * S: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0'
Traceback (most recent call last):
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/bin/ebuild-ipc.py", line 228, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/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_.zciy5m/pym/portage/locks.py", line 103, in lockfile
    myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/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/dev-libs/boost-1.49.0-r2/.ipc_lock'
 * The ebuild phase 'install' 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/._portage_reinstall_.zciy5m/bin/misc-functions.sh: line 1246: /var/tmp/portage/dev-libs/boost-1.49.0-r2/.die_hooks: No space left on device
Traceback (most recent call last):
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/bin/ebuild-ipc.py", line 228, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/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_.zciy5m/pym/portage/locks.py", line 103, in lockfile
    myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
  File "/var/tmp/portage/._portage_reinstall_.zciy5m/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/dev-libs/boost-1.49.0-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 dev-libs/boost-1.49.0-r2:
 * The ebuild phase 'install' 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.
 * ERROR: dev-libs/boost-1.49.0-r2 failed (install phase):
 *   Installation of Boost libraries failed
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_install
 *   environment, line 5392:  Called installation
 *   environment, line 5361:  Called die
 * The specific snippet of code:
 *           ${BJAM} -q -d+2 gentoorelease --user-config=user-config.jam ${OPTIONS} threading=single,multi ${LINK_OPTS} runtime-link=shared --includedir="${D}usr/include" --libdir="${D}usr/$(get_libdir)" $(use python && echo --python-buildid=${PYTHON_ABI}) install || die "Installation of Boost libraries failed";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/boost-1.49.0-r2'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.49.0-r2'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0'
 * S: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0'



!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1389, in build_packages
    "Error in attempt to build packages",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: livecdbuild 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 1394, in build_packages
    "build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage1
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20130813/.catalyst_lock'



Full build log at /tmp/catalyst-auto.22141/log/installcd-stage1.log