[gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec

Setting hash_function to config file value "crc32"
Setting storedir to config file value "/release/buildroot/amd64-dev"
Setting portdir to config file value "/release/trees/portage-auto"
Setting distdir to config file value "/release/tmp/distfiles/"
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Preserving libs during unmerge.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage4
Building natively for amd64
Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20170831/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 
clearing autoresume ...
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to untar...
No Valid Resume point detected, cleaning up...
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/

Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ (This may take some time) ...

tar: SELinux support is not available
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Configuring profile link...
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- Running action sequence: portage_overlay
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...

Warning!!!!
	Overriding certain env variables may cause catastrophic failure.
	If your build fails look here first as the possible problem.
	Catalyst assumes you know what you are doing when setting
		these variables.
	Catalyst Maintainers use VERY minimal envscripts if used at all
	You have been warned

--- Running action sequence: setup_environment
--- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831//tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-devel/binutils-2.28.1::gentoo
>>> Failed to emerge sys-devel/binutils-2.28.1, Log file:
>>>  '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log'
 * Package:    sys-devel/binutils-2.28.1
 * Repository: gentoo
 * Maintainer: toolchain@g.o
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux nls userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-devel/binutils-2.28.1/work': No such file or directory
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * ERROR: sys-devel/binutils-2.28.1::gentoo failed (unpack phase):
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 *   Failed to create dir '/var/tmp/portage/sys-devel/binutils-2.28.1/work'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * 
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * Call stack:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 *            ebuild.sh, line  767:  Called __ebuild_main 'unpack'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 *   phase-functions.sh, line 1008:  Called __dyn_unpack
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 *   phase-functions.sh, line  240:  Called die
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * The specific snippet of code:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 *   		install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'"
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * 
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.28.1::gentoo'`,
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.28.1::gentoo'`.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/environment'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * Working directory: '/var/tmp/portage/sys-devel/binutils-2.28.1/homedir'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
 * S: '/var/tmp/portage/sys-devel/binutils-2.28.1/work/binutils-2.28.1'
 * ACCESS DENIED:  open_wr:      /usr/lib64/python3.4/site-packages/aayc8gmb
Traceback (most recent call last):
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 282, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 279, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 136, in communicate
    lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 194, in lockfile
    locking_method = portage._eintr_func_wrapper(_get_lock_fn())
  File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 62, in _get_lock_fn
    fd, lock_path = tempfile.mkstemp()
  File "/usr/lib64/python3.4/tempfile.py", line 271, in mkstemp
    dir = gettempdir()
  File "/usr/lib64/python3.4/tempfile.py", line 239, in gettempdir
    tempdir = _get_default_tempdir()
  File "/usr/lib64/python3.4/tempfile.py", line 180, in _get_default_tempdir
    dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.4/site-packages']
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/log/sandbox/sandbox-18323.log"
 * --------------------------------------------------------------------------------
 * 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.
 * Messages for package sys-devel/binutils-2.28.1:
 * 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: Error in attempt to build packages


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

!!! catalyst: stage4build aborting due to error.

Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1333, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1437, in build_packages
    "build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/.catalyst_lock'
Command exited with non-zero status 1
34.53user 6.04system 0:24.61elapsed 164%CPU (0avgtext+0avgdata 844784maxresident)k
3984inputs+1815176outputs (0major+292809minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20170831.IkLA0t/log/hardened_stage4-nomultilib-cloud.log