[gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - stage2.spec

[root]

Makefile:622: recipe for target 'compatibility-debug_list.lo' failed
make[6]: *** [compatibility-debug_list.lo] Error 1
make[6]: *** Waiting for unfinished jobs....
{standard input}: Assembler messages:
{standard input}: Fatal error: can't write 28 bytes to section .text._ZNSt11char_traitsIcE4eqXXERKcS2_ of .libs/compatibility.o because: 'No space left on device'
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
/usr/s390x-ibm-linux-gnu/bin/as: BFD (Gentoo 2.29.1 p3) 2.29.1 assertion fail /var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/bfd/elf.c:3078
{standard input}: Fatal error: can't close .libs/compatibility.o: No space left on device
Makefile:622: recipe for target 'compatibility.lo' failed
make[6]: *** [compatibility.lo] Error 1
make[6]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build/s390x-ibm-linux-gnu/libstdc++-v3/src'
Makefile:637: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build/s390x-ibm-linux-gnu/libstdc++-v3/src'
Makefile:507: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build/s390x-ibm-linux-gnu/libstdc++-v3'
Makefile:414: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build/s390x-ibm-linux-gnu/libstdc++-v3'
Makefile:12911: recipe for target 'all-stage2-target-libstdc++-v3' failed
make[2]: *** [all-stage2-target-libstdc++-v3] Error 2
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build'
Makefile:17296: recipe for target 'stage2-bubble' failed
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build'
Makefile:17510: recipe for target 'bootstrap-lean' failed
make: *** [bootstrap-lean] Error 2
 * ERROR: sys-devel/gcc-5.4.0-r4::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-5.4.0-r4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-5.4.0-r4::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/gcc-5.4.0'
 * ACCESS DENIED:  open_wr:      /usr/lib64/python3.5/site-packages/0oj563x6
Traceback (most recent call last):
  File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 282, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 279, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 136, in communicate
    lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  File "/usr/lib64/python3.5/site-packages/portage/locks.py", line 194, in lockfile
    locking_method = portage._eintr_func_wrapper(_get_lock_fn())
  File "/usr/lib64/python3.5/site-packages/portage/locks.py", line 62, in _get_lock_fn
    fd, lock_path = tempfile.mkstemp()
  File "/usr/lib64/python3.5/tempfile.py", line 335, in mkstemp
    prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)
  File "/usr/lib64/python3.5/tempfile.py", line 130, in _sanitize_params
    dir = gettempdir()
  File "/usr/lib64/python3.5/tempfile.py", line 296, in gettempdir
    tempdir = _get_default_tempdir()
  File "/usr/lib64/python3.5/tempfile.py", line 231, in _get_default_tempdir
    dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp', '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp', '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.5/site-packages']
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/log/sandbox/sandbox-13798.log"
 * --------------------------------------------------------------------------------
 * The ebuild phase 'compile' 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.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/gcc-build-logs.tar.bz2 in your bug report.
 * 
 * Messages for package sys-apps/baselayout-2.4.1-r2:
 * The following users have non-existent shells!
 * halt - /sbin/halt
 * shutdown - /sbin/shutdown
 * You should reboot now to get /run mounted with tmpfs!
 * Messages for package sys-devel/gcc-5.4.0-r4:
 * The ebuild phase 'compile' 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: sys-devel/gcc-5.4.0-r4::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-5.4.0-r4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-5.4.0-r4::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/gcc-5.4.0'
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-5.4.0-r4/work/gcc-build-logs.tar.bz2 in your bug report.
 * 





!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1244, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build 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 1304, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1249, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage2
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage2-s390x-20180228T101246Z/.catalyst_lock'
Command exited with non-zero status 1
3148.08user 309.92system 32:20.78elapsed 178%CPU (0avgtext+0avgdata 3670304maxresident)k
0inputs+0outputs (1793major+163393180minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20180228T101246Z.0pii04/log/stage2.log