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

[root]

*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f netboot/netboot.spec
04 Oct 2019 21:43:45 EDT: NOTICE  : Loading configuration file: /etc/catalyst/catalyst.conf
04 Oct 2019 21:43:45 EDT: NOTICE  : conf_values[options] = {'kerncache', 'autoresume', 'seedcache', 'pkgcache', 'clear-autoresume', 'bindist', 'snapcache'}
04 Oct 2019 21:43:45 EDT: NOTICE  : Processing spec file: netboot/netboot.spec
04 Oct 2019 21:43:46 EDT: NOTICE  : Using target: netboot2
04 Oct 2019 21:43:46 EDT: NOTICE  : Source file specification matching setting is: strict
04 Oct 2019 21:43:46 EDT: NOTICE  : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
04 Oct 2019 21:43:50 EDT: NOTICE  : Source path set to /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.xz
04 Oct 2019 21:43:50 EDT: NOTICE  : Removing AutoResume Points ...
04 Oct 2019 21:43:50 EDT: NOTICE  : Emptying directory: /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20191004T194403Z
04 Oct 2019 21:43:50 EDT: NOTICE  : --- Running action sequence: unpack
04 Oct 2019 21:43:50 EDT: NOTICE  : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
04 Oct 2019 21:43:50 EDT: NOTICE  : Resume: "seed source" unpack resume point is disabled
04 Oct 2019 21:43:50 EDT: NOTICE  : Resume: Target chroot is invalid, cleaning up...
04 Oct 2019 21:43:50 EDT: NOTICE  : Removing AutoResume Points ...
04 Oct 2019 21:43:50 EDT: NOTICE  : Emptying directory: /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20191004T194403Z
04 Oct 2019 21:43:50 EDT: NOTICE  : Clearing the chroot path ...
04 Oct 2019 21:43:50 EDT: NOTICE  : Emptying directory: /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z
04 Oct 2019 21:43:50 EDT: NOTICE  : Starting auto from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.xz
04 Oct 2019 21:43:50 EDT: NOTICE  : to /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z (this may take some time) ..
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: unpack_snapshot
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: config_profile_link
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: setup_confdir
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: portage_overlay
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: bind
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: chroot_setup
04 Oct 2019 21:44:21 EDT: NOTICE  : Setting up chroot...
04 Oct 2019 21:44:21 EDT: WARNING : Overriding certain env variables may cause catastrophic failure.
04 Oct 2019 21:44:21 EDT: WARNING : If your build fails look here first as the possible problem.
04 Oct 2019 21:44:21 EDT: WARNING : Catalyst assumes you know what you are doing when setting these variables.
04 Oct 2019 21:44:21 EDT: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
04 Oct 2019 21:44:21 EDT: WARNING : You have been warned.
04 Oct 2019 21:44:21 EDT: NOTICE  : Writing the stage make.conf to: /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z/etc/portage/make.conf
04 Oct 2019 21:44:21 EDT: NOTICE  : STICKY-CONFIG is enabled
04 Oct 2019 21:44:21 EDT: WARNING : The use of -* in netboot2/use will cause portage to ignore
04 Oct 2019 21:44:21 EDT: WARNING : package.use in the profile and portage_confdir.
04 Oct 2019 21:44:21 EDT: WARNING : You've been warned!
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: setup_environment
04 Oct 2019 21:44:21 EDT: NOTICE  : --- Running action sequence: build_packages
>>> Building packages ...
Copying netboot2-pkg.sh to /tmp
copying netboot2-pkg.sh to /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z/tmp
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z/tmp
Ensure the file has the executable bit set
Running netboot2-pkg.sh in chroot:
    chroot /var/tmp/catalyst/tmp/default/netboot2-s390x-20191004T194403Z /tmp/netboot2-pkg.sh
>>> Regenerating /etc/ld.so.cache...
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse sys-apps/s390-tools sys-fs/e2fsprogs sys-apps/util-linux app-editors/nano sys-libs/ncurses dev-libs/popt net-misc/wget net-misc/rsync dev-libs/libtommath net-misc/dropbear dev-libs/openssl app-misc/screen sys-devel/bc

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


>>> Verifying ebuild manifests
>>> Emerging (1 of 14) sys-libs/ncurses-6.1_p20181020::gentoo
>>> Failed to emerge sys-libs/ncurses-6.1_p20181020, Log file:
>>>  '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp/build.log'
 * Package:    sys-libs/ncurses-6.1_p20181020
 * Repository: gentoo
 * Maintainer: base-system@g.o
 * USE:        abi_s390_64 elibc_glibc kernel_linux s390 split-usr tinfo unicode userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
/usr/lib/portage/python3.6/ebuild.sh: line 408: cannot create temp file for here-document: No space left on device
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/work': No such file or directory
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * ERROR: sys-libs/ncurses-6.1_p20181020::gentoo failed (unpack phase):
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 *   Failed to create dir '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/work'
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * 
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * Call stack:
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 *            ebuild.sh, line  781:  Called __ebuild_main 'unpack'
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 *   phase-functions.sh, line 1072:  Called __dyn_unpack
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 *   phase-functions.sh, line  252:  Called die
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * The specific snippet of code:
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: 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.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * 
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * If you need support, post the output of `emerge --info '=sys-libs/ncurses-6.1_p20181020::gentoo'`,
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * the complete build log and the output of `emerge -pqv '=sys-libs/ncurses-6.1_p20181020::gentoo'`.
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * The complete build log is located at '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp/build.log'.
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp/environment'.
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * Working directory: '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/homedir'
/usr/lib/portage/python3.6/isolated-functions.sh: line 270: echo: write error: No space left on device
 * S: '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/work/ncurses-6.1'
 * ACCESS DENIED:  open_wr:      /usr/lib64/python3.6/site-packages/2k4p7n5g
Traceback (most recent call last):
  File "/usr/lib/portage/python3.6/ebuild-ipc.py", line 277, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/usr/lib/portage/python3.6/ebuild-ipc.py", line 273, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/usr/lib/portage/python3.6/ebuild-ipc.py", line 130, in communicate
    lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  File "/usr/lib64/python3.6/site-packages/portage/locks.py", line 113, in lockfile
    unlinkfile=unlinkfile, waiting_msg=waiting_msg, flags=flags)
  File "/usr/lib64/python3.6/site-packages/portage/locks.py", line 221, in _lockfile_iteration
    locking_method = portage._eintr_func_wrapper(_get_lock_fn())
  File "/usr/lib64/python3.6/site-packages/portage/locks.py", line 63, in _get_lock_fn
    fd, lock_path = tempfile.mkstemp()
  File "/usr/lib64/python3.6/tempfile.py", line 335, in mkstemp
    prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)
  File "/usr/lib64/python3.6/tempfile.py", line 130, in _sanitize_params
    dir = gettempdir()
  File "/usr/lib64/python3.6/tempfile.py", line 296, in gettempdir
    tempdir = _get_default_tempdir()
  File "/usr/lib64/python3.6/tempfile.py", line 231, in _get_default_tempdir
    dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp', '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp', '/var/tmp/portage/sys-libs/ncurses-6.1_p20181020/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.6/site-packages']
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/log/sandbox/sandbox-4.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-libs/ncurses-6.1_p20181020:
 * 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.


04 Oct 2019 21:44:32 EDT: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/netboot2/netboot2-controller.sh', 'build_packages', 'sys-apps/s390-tools', 'sys-fs/e2fsprogs', 'sys-apps/util-linux', 'app-editors/nano', 'sys-libs/ncurses', 'dev-libs/popt', 'net-misc/wget', 'net-misc/rsync', 'dev-libs/libtommath', 'net-misc/dropbear', 'dev-libs/openssl', 'app-misc/screen', 'sys-devel/bc']) exited 1
04 Oct 2019 21:44:32 EDT: ERROR   : CatalystError: netboot2build aborting due to error.
04 Oct 2019 21:44:32 EDT: ERROR   : Exception running action sequence build_packages
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1561, in build_packages
    cmd(command, env=self.env)
  File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
    print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/netboot2/netboot2-controller.sh', 'build_packages', 'sys-apps/s390-tools', 'sys-fs/e2fsprogs', 'sys-apps/util-linux', 'app-editors/nano', 'sys-libs/ncurses', 'dev-libs/popt', 'net-misc/wget', 'net-misc/rsync', 'dev-libs/libtommath', 'net-misc/dropbear', 'dev-libs/openssl', 'app-misc/screen', 'sys-devel/bc']) exited 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
    getattr(self, x)()
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1568, in build_packages
    "build aborting due to error.")
catalyst.support.CatalystError: netboot2build aborting due to error.
04 Oct 2019 21:44:32 EDT: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
20.93user 2.34system 0:47.49elapsed 49%CPU (0avgtext+0avgdata 509792maxresident)k
0inputs+0outputs (39major+298328minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20191004T194403Z.97IVhj/log/netboot_netboot.log