Gentoo Archives: gentoo-releng-autobuilds

From: root <vapier@g.o>
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - netboot/netboot.spec
Date: Thu, 20 Sep 2018 14:25:34
Message-Id: 20180920142527.81CF320543@nightheron.gentoo.org
Distributed under the GNU General Public License version 2.1

Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib64/catalyst"
Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume bindist kerncache pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: netboot2
Building natively for s390
Source path set to /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20180920T091130Z/
The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20180920T091130Z/
Location of the package cache is /var/tmp/catalyst/packages/default/netboot2-s390x-20180920T091130Z/
Location of the kerncache is /var/tmp/catalyst/kerncache/default/netboot2-s390x-20180920T091130Z/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20180920T091130Z/
--- 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 /var/tmp/catalyst/tmp/default/.autoresume-netboot2-s390x-20180920T091130Z/
Emptying directory /var/tmp/catalyst/tmp/default/netboot2-s390x-20180920T091130Z/

Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2
to /var/tmp/catalyst/tmp/default/netboot2-s390x-20180920T091130Z/ (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


Warning!!!  
	The use of -* in netboot2/use will cause portage to ignore
	package.use in the profile and portage_confdir. You've been warned!
--- Running action sequence: setup_environment
--- 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-20180920T091130Z//tmp copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-s390x-20180920T091130Z//tmp Ensure the file has the executable bit set Running netboot2-pkg.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-s390x-20180920T091130Z/
>>> Regenerating /etc/ld.so.cache... >>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --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 13) sys-libs/ncurses-6.1-r2::gentoo >>> Failed to emerge sys-libs/ncurses-6.1-r2, Log file: >>> '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/build.log'
* Package: sys-libs/ncurses-6.1-r2 * Repository: gentoo * Maintainer: base-system@g.o * USE: abi_s390_64 elibc_glibc kernel_linux s390 unicode userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox /usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work': No such file or directory /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * ERROR: sys-libs/ncurses-6.1-r2::gentoo failed (unpack phase): /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * Failed to create dir '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work' /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * Call stack: /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * ebuild.sh, line 792: Called __ebuild_main 'unpack' /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * phase-functions.sh, line 1067: Called __dyn_unpack /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * phase-functions.sh, line 251: Called die /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * The specific snippet of code: /usr/lib/portage/python3.5/isolated-functions.sh: line 272: 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.5/isolated-functions.sh: line 272: echo: write error: No space left on device * /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * If you need support, post the output of `emerge --info '=sys-libs/ncurses-6.1-r2::gentoo'`, /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * the complete build log and the output of `emerge -pqv '=sys-libs/ncurses-6.1-r2::gentoo'`. /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * The complete build log is located at '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/build.log'. /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * The ebuild environment file is located at '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp/environment'. /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * Working directory: '/var/tmp/portage/sys-libs/ncurses-6.1-r2/homedir' /usr/lib/portage/python3.5/isolated-functions.sh: line 272: echo: write error: No space left on device * S: '/var/tmp/portage/sys-libs/ncurses-6.1-r2/work/ncurses-6.1' * ACCESS DENIED: open_wr: /usr/lib64/python3.5/site-packages/9xubi4q3 Traceback (most recent call last): File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 277, in <module> sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 273, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/usr/lib/portage/python3.5/ebuild-ipc.py", line 130, 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-libs/ncurses-6.1-r2/temp', '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp', '/var/tmp/portage/sys-libs/ncurses-6.1-r2/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.5/site-packages'] * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-26779.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-r2: * 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 1403, 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: netboot2build 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 1408, in build_packages "build aborting due to error." CatalystError !!! catalyst: Error encountered during run of target netboot2 Catalyst aborting.... lockfile does not exist '/var/tmp/catalyst/tmp/default/netboot2-s390x-20180920T091130Z/.catalyst_lock' Command exited with non-zero status 1 20.48user 2.03system 0:18.41elapsed 122%CPU (0avgtext+0avgdata 259088maxresident)k 0inputs+0outputs (34major+324068minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20180920T091130Z.0IQxqF/log/netboot_netboot.log