* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2018-08-04 20:33 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2018-08-04 20:33 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
04 Aug 2018 16:56:07 UTC: WARNING : You have been warned.
04 Aug 2018 16:56:07 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/etc/portage/make.conf
04 Aug 2018 16:56:07 UTC: NOTICE : STICKY-CONFIG is enabled
04 Aug 2018 16:56:07 UTC: NOTICE : --- Running action sequence: setup_environment
04 Aug 2018 16:56:07 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
>>> Emerging binary (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
>>> Installing (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
>>> Emerging binary (1 of 3) sys-apps/busybox-1.28.0::gentoo
>>> Installing (1 of 3) sys-apps/busybox-1.28.0::gentoo
>>> Emerging binary (2 of 3) net-misc/iputils-20171016_pre::gentoo
>>> Installing (2 of 3) net-misc/iputils-20171016_pre::gentoo
>>> Emerging binary (3 of 3) sys-apps/util-linux-2.32-r4::gentoo
>>> Installing (3 of 3) sys-apps/util-linux-2.32-r4::gentoo
* Messages for package net-misc/iputils-20171016_pre:
* Log file: /home/release/tmp/logs/net-misc:iputils-20171016_pre:20180804-165634.log
* Could not find cap utils; make sure libcap or libcap-ng is available.
* Messages for package sys-apps/util-linux-2.32-r4:
* Log file: /home/release/tmp/logs/sys-apps:util-linux-2.32-r4:20180804-165637.log
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse net-misc/dhcp net-misc/iputils sys-boot/grub sys-apps/gptfdisk sys-apps/iproute2 sys-devel/bc sys-power/acpid
>>> Running pre-merge checks for sys-power/acpid-2.0.29-r1
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging binary (1 of 9) sys-power/acpid-2.0.29-r1::gentoo
>>> Installing (1 of 9) sys-power/acpid-2.0.29-r1::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging binary (2 of 9) sys-libs/efivar-31::gentoo
>>> Installing (2 of 9) sys-libs/efivar-31::gentoo
>>> Emerging binary (3 of 9) virtual/libudev-232::gentoo
>>> Installing (3 of 9) virtual/libudev-232::gentoo
>>> Emerging binary (4 of 9) net-misc/dhcp-4.3.6_p1::gentoo
>>> Installing (4 of 9) net-misc/dhcp-4.3.6_p1::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging binary (5 of 9) sys-apps/gptfdisk-1.0.3::gentoo
>>> Installing (5 of 9) sys-apps/gptfdisk-1.0.3::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging binary (6 of 9) sys-devel/bc-1.06.95-r2::gentoo
>>> Installing (6 of 9) sys-devel/bc-1.06.95-r2::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging binary (7 of 9) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (7 of 9) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging binary (8 of 9) sys-boot/efibootmgr-15::gentoo
>>> Installing (8 of 9) sys-boot/efibootmgr-15::gentoo
>>> Emerging binary (9 of 9) sys-boot/grub-2.02-r1::gentoo
>>> Installing (9 of 9) sys-boot/grub-2.02-r1::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
* Messages for package sys-power/acpid-2.0.29-r1:
* Log file: /home/release/tmp/logs/sys-power:acpid-2.0.29-r1:20180804-165642.log
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package sys-power/acpid-2.0.29-r1:
* Log file: /home/release/tmp/logs/sys-power:acpid-2.0.29-r1:20180804-165642.log
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package sys-boot/grub-2.02-r1:
* Log file: /home/release/tmp/logs/sys-boot:grub-2.02-r1:20180804-165656.log
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp/stage4-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp/chroot-functions.sh from the chroot
04 Aug 2018 16:57:02 UTC: NOTICE : --- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z /tmp/pre-kmerge.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Running pre-merge checks for sys-kernel/genkernel-3.5.3.3
>>> Emerging binary (1 of 3) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 3) app-arch/cpio-2.12-r1::gentoo
>>> Emerging binary (2 of 3) sys-kernel/linux-firmware-20180103-r2::gentoo
>>> Installing (2 of 3) sys-kernel/linux-firmware-20180103-r2::gentoo
>>> Emerging binary (3 of 3) sys-kernel/genkernel-3.5.3.3::gentoo
>>> Installing (3 of 3) sys-kernel/genkernel-3.5.3.3::gentoo
* Messages for package sys-kernel/linux-firmware-20180103-r2:
* Log file: /home/release/tmp/logs/sys-kernel:linux-firmware-20180103-r2:20180804-165707.log
* If you are only interested in particular firmware files, edit the saved
* configfile and remove those that you do not want.
* Messages for package sys-kernel/genkernel-3.5.3.3:
* Log file: /home/release/tmp/logs/sys-kernel:genkernel-3.5.3.3:20180804-165722.log
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp/pre-kmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z/tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20180804T134746Z /tmp/kmerge.sh
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.5.3.3 found ... OK
emerge --quiet --usepkg --buildpkg --newuse gentoo-sources
>>> Emerging binary (1 of 1) sys-kernel/gentoo-sources-4.14.52::gentoo
>>> Installing (1 of 1) sys-kernel/gentoo-sources-4.14.52::gentoo
>>> Recording sys-kernel/gentoo-sources in "world" favorites file...
* Messages for package sys-kernel/gentoo-sources-4.14.52:
* Log file: /home/release/tmp/logs/sys-kernel:gentoo-sources-4.14.52:20180804-165728.log
* If you are upgrading from a previous kernel, you may be interested
* in the following document:
* - General upgrade guide: https://wiki.gentoo.org/wiki/Kernel/Upgrade
Adjusting /usr/src/linux to point to /usr/src/linux-4.14.52-gentoo
Setting extraversion to openstack
^[[32;01m*^[[32;01m Gentoo Linux Genkernel; Version 3.5.3.3^[[0m
^[[32;01m*^[[0m Running with options: --all-ramdisk-modules --cachedir=/tmp/kerncache/gentoo-genkernel_cache-minimal-nomultilib-20180804T134746Z --no-mountboot --kerneldir=/usr/src/linux --modulespackage=/tmp/kerncache/gentoo-modules-minimal-nomultilib-20180804T134746Z.tar.bz2 --minkernpackage=/tmp/kerncache/gentoo-kernel-initrd-minimal-nomultilib-20180804T134746Z.tar.bz2 all --kernel-config=/var/tmp/gentoo.config
^[[32;01m*^[[0m Using genkernel.conf from /etc/genkernel.conf
^[[32;01m*^[[0m Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh ..
^[[32;01m*^[[0m Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load ..
^[[32;01m*^[[0;01m Linux Kernel ^[[0;01m4.14.52-gentoo-openstack^[[0m for ^[[0;01mx86_64^[[0m...
^[[32;01m*^[[0m .. with config file /var/tmp/gentoo.config
^[[32;01m*^[[0m kernel: Using config from /var/tmp/gentoo.config
^[[32;01m*^[[0m kernel: >> Running mrproper...
^[[32;01m*^[[0m >> Running oldconfig...
^[[32;01m*^[[0m kernel: >> Cleaning...
^[[32;01m*^[[0m >> Compiling 4.14.52-gentoo-openstack bzImage...
Killed
04 Aug 2018 20:33:07 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited 1
04 Aug 2018 20:33:07 UTC: ERROR : CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1575, in build_kernel
self._build_kernel(kname = kname)
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1612, in _build_kernel
env=self.env)
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited 1
04 Aug 2018 20:33:07 UTC: ERROR : Exception running action sequence build_kernel
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1575, in build_kernel
self._build_kernel(kname = kname)
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1612, in _build_kernel
env=self.env)
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1581, in build_kernel
print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
04 Aug 2018 20:33:07 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
117.12user 14.34system 3:37:15elapsed 1%CPU (0avgtext+0avgdata 359388maxresident)k
0inputs+6038592outputs (0major+5572998minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20180804T134746Z.GzUfBv/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-03-02 16:10 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-03-02 16:10 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-nomultilib-minimal.spec
02 Mar 2019 16:09:39 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:09:39 UTC: NOTICE : conf_values[options] = {'pkgcache', 'preserve_libs', 'bindist', 'clear-autoresume'}
02 Mar 2019 16:09:40 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
02 Mar 2019 16:09:40 UTC: NOTICE : Using target: stage4
02 Mar 2019 16:09:40 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:09:40 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
02 Mar 2019 16:09:40 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:09:40 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:09:40 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:09:40 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z
02 Mar 2019 16:09:40 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:09:40 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z (this may take some time) ..
02 Mar 2019 16:09:44 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:09:44 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: config_profile_link
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:10:21 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:10:21 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:10:21 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:10:21 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:10:21 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:10:21 UTC: WARNING : You have been warned.
02 Mar 2019 16:10:21 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z/etc/portage/make.conf
02 Mar 2019 16:10:21 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:10:21 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T160623Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
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.)
* Last emerge --sync was 210d 3h 5m 25s ago.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.40-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161027.log'
* Package: sys-apps/portage-2.3.40-r1
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 userland_GNU xattr
* FEATURES: preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161027.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
* Messages for package sys-apps/portage-2.3.40-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161027.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161027.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
02 Mar 2019 16:10:35 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
02 Mar 2019 16:10:36 UTC: ERROR : CatalystError: stage4build aborting due to error.
02 Mar 2019 16:10:36 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1551, 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/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) 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 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1558, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
02 Mar 2019 16:10:36 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
31.68user 4.19system 0:56.28elapsed 63%CPU (0avgtext+0avgdata 357796maxresident)k
136inputs+3626976outputs (0major+506581minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-03-02 16:22 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-03-02 16:22 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-nomultilib-minimal.spec
02 Mar 2019 16:22:33 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:22:33 UTC: NOTICE : conf_values[options] = {'bindist', 'clear-autoresume', 'preserve_libs', 'pkgcache'}
02 Mar 2019 16:22:33 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
02 Mar 2019 16:22:33 UTC: NOTICE : Using target: stage4
02 Mar 2019 16:22:33 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:22:33 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
02 Mar 2019 16:22:33 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:22:33 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:22:33 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:22:33 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z
02 Mar 2019 16:22:33 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:22:33 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z (this may take some time) ..
02 Mar 2019 16:22:37 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:22:37 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: config_profile_link
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:22:47 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:22:47 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:22:47 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:22:47 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:22:47 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:22:47 UTC: WARNING : You have been warned.
02 Mar 2019 16:22:47 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z/etc/portage/make.conf
02 Mar 2019 16:22:47 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:22:47 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190302T162037Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
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.)
>>> Emerging binary (1 of 1) sys-apps/portage-2.3.51-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.51-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162251.log'
>>> Extracting info
* Package: sys-apps/portage-2.3.51-r1
* Repository: gentoo
* USE: amd64 abi_x86_64 native-extensions kernel_linux elibc_glibc ipc python_targets_python2_7 xattr userland_GNU python_targets_python3_6
* FEATURES: preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 792: Called __ebuild_main 'setup'
* phase-functions.sh, line 984: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162251.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
* Messages for package sys-apps/portage-2.3.51-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162251.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 792: Called __ebuild_main 'setup'
* phase-functions.sh, line 984: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162251.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
02 Mar 2019 16:22:53 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
02 Mar 2019 16:22:53 UTC: ERROR : CatalystError: stage4build aborting due to error.
02 Mar 2019 16:22:53 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1551, 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/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) 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 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1558, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
02 Mar 2019 16:22:53 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.28user 4.17system 0:20.87elapsed 165%CPU (0avgtext+0avgdata 358008maxresident)k
336inputs+3654504outputs (0major+331186minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-06-11 1:30 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-11 1:30 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-nomultilib-minimal.spec
11 Jun 2019 01:29:51 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 01:29:51 UTC: NOTICE : conf_values[options] = {'bindist', 'pkgcache', 'preserve_libs', 'clear-autoresume'}
11 Jun 2019 01:29:51 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
11 Jun 2019 01:29:51 UTC: NOTICE : Using target: stage4
11 Jun 2019 01:29:51 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 01:29:51 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 01:29:51 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
11 Jun 2019 01:29:51 UTC: NOTICE : --- Running action sequence: unpack
11 Jun 2019 01:29:51 UTC: NOTICE : Clearing the chroot path ...
11 Jun 2019 01:29:51 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z
11 Jun 2019 01:29:51 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
11 Jun 2019 01:29:51 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z (this may take some time) ..
11 Jun 2019 01:29:55 UTC: NOTICE : --- Running action sequence: unpack_snapshot
11 Jun 2019 01:29:55 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: config_profile_link
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: setup_confdir
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: portage_overlay
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: bind
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: chroot_setup
11 Jun 2019 01:30:31 UTC: NOTICE : Setting up chroot...
11 Jun 2019 01:30:31 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
11 Jun 2019 01:30:31 UTC: WARNING : If your build fails look here first as the possible problem.
11 Jun 2019 01:30:31 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
11 Jun 2019 01:30:31 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
11 Jun 2019 01:30:31 UTC: WARNING : You have been warned.
11 Jun 2019 01:30:31 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z/etc/portage/make.conf
11 Jun 2019 01:30:31 UTC: NOTICE : STICKY-CONFIG is enabled
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: setup_environment
11 Jun 2019 01:30:31 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-nomultilib-20190611T012607Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse --oneshot --update --newuse sys-apps/portage
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-apps/portage-2.3.62-r2
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 1) sys-apps/portage-2.3.62-r2::gentoo
>>> Failed to emerge sys-apps/portage-2.3.62-r2, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013048.log'
* Package: sys-apps/portage-2.3.62-r2
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify userland_GNU xattr
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 598: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013048.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'
* Messages for package sys-apps/portage-2.3.62-r2:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013048.log
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package sys-apps/portage-2.3.62-r2:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013048.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 598: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013048.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'
11 Jun 2019 01:30:49 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
11 Jun 2019 01:30:49 UTC: ERROR : CatalystError: stage4build aborting due to error.
11 Jun 2019 01:30:49 UTC: 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/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) 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: stage4build aborting due to error.
11 Jun 2019 01:30:49 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
32.84user 4.77system 0:58.85elapsed 63%CPU (0avgtext+0avgdata 356568maxresident)k
3856inputs+3874024outputs (0major+629579minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-06-11 9:26 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-11 9:26 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-nomultilib-minimal.spec
11 Jun 2019 09:26:46 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 09:26:46 UTC: NOTICE : conf_values[options] = {'bindist', 'preserve_libs', 'clear-autoresume', 'pkgcache'}
11 Jun 2019 09:26:46 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
11 Jun 2019 09:26:46 UTC: NOTICE : Using target: stage4
11 Jun 2019 09:26:46 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 09:26:46 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 09:26:47 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/default/stage3-amd64-nomultilib-latest
Command exited with non-zero status 2
0.21user 0.01system 0:00.27elapsed 84%CPU (0avgtext+0avgdata 18200maxresident)k
0inputs+0outputs (0major+9498minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T092541Z.nNqC3R/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-06-14 18:35 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-14 18:35 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-nomultilib-minimal.spec
14 Jun 2019 18:35:33 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
14 Jun 2019 18:35:33 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'bindist', 'pkgcache', 'clear-autoresume'}
14 Jun 2019 18:35:33 UTC: NOTICE : Processing spec file: stage4-nomultilib-minimal.spec
14 Jun 2019 18:35:33 UTC: NOTICE : Using target: stage4
14 Jun 2019 18:35:33 UTC: NOTICE : Source file specification matching setting is: loose
14 Jun 2019 18:35:33 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
14 Jun 2019 18:35:34 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/default/stage3-amd64-nomultilib-latest
Command exited with non-zero status 2
0.22user 0.00system 0:00.30elapsed 75%CPU (0avgtext+0avgdata 18304maxresident)k
0inputs+0outputs (0major+9475minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190614T183511Z.BWvov2/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec
@ 2019-06-15 6:32 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-15 6:32 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
15 Jun 2019 06:32:42 UTC: NOTICE : to /home/release/buildroot/amd64-exp/tmp/default/stage4-amd64-minimal-nomultilib-20190614T185156Z (this may take some time) ..
tar: ./home/release/tmp/logs/dev-libs:gmp-6.1.2:20190614-222144.log: Wrote only 2048 of 10240 bytes
tar: ./home/release/tmp/logs/virtual\:tmpfiles-0\:20190614-221157.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-devel\:gcc-8.3.0-r1\:20190614-220646.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:file-5.36\:20190614-222450.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/virtual\:mta-1\:20190614-215723.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-process\:procps-3.3.15-r1\:20190614-221252.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-libs\:cracklib-2.9.6-r2\:20190614-222543.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/virtual\:modutils-0\:20190614-222640.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:net-tools-1.60_p20180626073013\:20190614-222032.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/virtual\:dev-manager-0-r2\:20190615-001939.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/net-firewall\:iptables-1.6.1-r3\:20190614-222703.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/virtual\:libffi-3.0.13-r1\:20190614-222613.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/dev-util\:pkgconf-1.5.4\:20190614-221109.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/virtual\:perl-Perl-OSType-1.10.0-r2\:20190614-221920.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/app-crypt\:pinentry-1.1.0-r2\:20190614-215622.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/app-eselect\:eselect-pinentry-0.7\:20190614-215026.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:portage-2.3.66-r1\:20190614-204628.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/dev-libs\:mpc-1.0.3\:20190614-222620.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-devel\:gcc-config-2.0\:20190614-221150.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-libs\:pam-1.3.0-r2\:20190615-001219.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/app-admin\:metalog-20181125\:20190614-221636.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-devel\:binutils-2.31.1-r6\:20190614-205313.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/app-portage\:elt-patches-20170815\:20190614-204803.log: Cannotar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/pb_ds/detail/cc_hash_table_map_/debug_store_hash_fn_imps.hpp: Cannot open: No such file or directory
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/functional: Wrote only 8192 of 8704 bytes
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/vstring.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/numeric_traits.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/rb_tree: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/numeric: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/sso_string_base.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/pod_char_traits.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/bitmap_allocator.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/hash_map: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/debug_allocator.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/random.tcc: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/alloc_traits.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/aligned_buffer.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/pool_allocator.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/pointer.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/concurrence.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/cast.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/string_conversions.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/throw_allocator.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/vstring_util.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ext/memory: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/cctype: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/algorithm: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/string_view: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/csetjmp: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/cfenv: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/ccomplex: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/stdexcept: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/future: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/cwctype: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/system_error: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/new: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/math.h: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/limits: Cannot write: No space left on device
tar: ./usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/cstdint: Cannot write: No space l: No space left on device
tar: ./usr/bin/ranlib: Cannot create symlink to 'x86_64-pc-linux-gnu-ranlib': No space left on device
tar: ./usr/bin/ptar: Cannot create symlink to 'ptar-2.300.0-perl-5.28.2': No space left on device
tar: ./usr/bin/asn1Coding: Cannot open: No space left on device
tar: ./usr/bin/podselect-1.630.0-perl-5.28.2: Cannot open: No space left on device
tar: ./usr/bin/tput: Cannot open: No space left on device
tar: ./usr/bin/zipinfo: Cannot create symlink to 'unzip': No space left on device
tar: ./usr/bin/gpg-error-config: Cannot create symlink to 'x86_64-pc-linux-gnu-gpg-error-config': No space left on device
tar: ./usr/bin/python-exec2c: Cannot open: No space left on device
tar: ./usr/bin/kbdinfo: Cannot open: No space left on device
tar: ./usr/bin/choom: Cannot open: No space left on device
tar: ./usr/bin/bzdiff: Cannot open: No space left on device
tar: ./usr/bin/ssh-agent: Cannot open: No space left on device
tar: ./usr/bin/gpgtar: Cannot open: No space left on device
tar: ./usr/bin/chfn: Cannot open: No space left on device
tar: ./usr/bin/install-info: Cannot open: No space left on device
tar: ./usr/bin/pathchk: Cannot open: No space left on device
tar: ./usr/bin/perlbug: Cannot hard link to './usr/bin/perlthanks': No space left on device
tar: ./usr/bin/gpgscm: Cannot open: No space left on device
tar: ./usr/bin/printenv: Cannot open: No space left on device
tar: ./usr/bin/du: Cannot open: No space left on device
tar: ./usr/bin/qpkg: Cannot create symlink to 'q': No space left on device
tar: ./usr/bin/ipcmk: Cannot open: No space left on device
tar: ./usr/bin/ionice: Cannot open: No space left on device
tar: ./usr/bin/last: Cannot open: No space left on device
tar: ./usr/bin/bashbug: Cannot open: No space left on device
tar: ./usr/bin/dumpsexp: Cannot open: No space left on device
tar: ./usr/bin/kbd_mode: Cannot open: No space left on device
tar: ./usr/bin/grog: Cannot open: No space left on device
tar: ./usr/bin/iconv: Cannot open: No space left on device
tar: ./usr/bin/x86_64-pc-linux-gnu-gcc-ranlib: Cannot open: No space left on device
tar: ./usr/bin/autoreconf: Cannot open: No space left on device
tar: ./usr/bin/ptx: Cannot open: No space left on device
tar: ./usr/bin/strings: Cannot create symlink to 'x86_64-pc-linux-gnu-strings': No space left on device
tar: ./usr/bin/users: Cannot open: No space left on device
tar: ./usr/bin/msgcat: Cannot open: No space left on device
tar: ./usr/bin/binutils-config: Cannot open: No space left on device
tar: ./usr/bin/pl2pm: Cannot open: No space left on device
tar: ./usr/bin/tset: Cannot open: No space left on device
tar: ./usr/bin/dir: Cannot open: No space left on device
tar: ./usr/bin/watch: Cannot open: No space left on device
tar: ./usr/bin/vmstat: Cannot open: No space left on device
tar: ./usr/bin/realpath: Cannot open: No space left on device
tar: ./usr/bin/ssh: Cannot open: No space left on device
tar: ./usr/bin/spent: Cannot create symlink to 'ospent': No space left on device
tar: ./usr/bin/getent: Cannot open: No space left on device
tar: ./usr/bin/qcheck: Cannot create symlink to 'q': No space left on device
tar: ./usr/bin/wget: Cannot open: No space left on device
tar: ./usr/bin/autoheader-2.69: Cannot open: No space left on device
tar: ./usr/bin/groffer: Cannot open: No space left on device
tar: ./usr/bin/db5.3_deadlock: Cannot open: No space left on device
tar: ./usr/bin/w: Cannot open: No space left on device
tar: ./usr/bin/ld.bfd: Cannot create symlink to 'x86_64-pc-linux-gnu-ld.bfd': No space left on device
tar: ./usr/bin/csplit: Cannot open: No space left on device
tar: ./usr/bin/mpicalc: Cannot open: No space left on device
tar: ./usr/bin/gcov-8.3.0: Cannot open: No space left on device
tar: ./usr/bin/qdepends: Cannot create symlink to 'q': No space left on device
tar: ./usr/bin/chem: Cannot open: No space left on device
tar: ./usr/bin/flex++: Cannot create symlink to 'flex': No space left on device
tar: ./usr/bin/x86_64-pc-linux-gnu-cpp-8.3.0: Cannot open: No space left on device
tar: ./usr/bin/hmac256: Cannot open: No space left on dev--- Logging error ---
Traceback (most recent call last):
File "/usr/lib64/python3.6/logging/__init__.py", line 998, in emit
self.flush()
File "/usr/lib64/python3.6/logging/__init__.py", line 978, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.6/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 285, in main
return _main(parser, opts)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 452, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 114, in build_target
return target.run()
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 824, in unpack
log.error('%s', error_msg % unpack_info)
File "/usr/lib64/python3.6/logging/__init__.py", line 1337, in error
self._log(ERROR, msg, args, **kwargs)
File "/usr/lib64/python3.6/site-packages/catalyst/log.py", line 29, in _log
super(CatalystLogger, self)._log(level, line, (), **kwargs)
Message: "'pixz' extraction of /home/release/buildroot/amd64-exp/builds/default/stage3-amd64-nomultilib-latest.tar.xz to /home/release/buildroot/amd64-exp/tmp/default/stage4-amd64-minimal-nomultilib-20190614T185156Z failed."
Arguments: ()
--- Logging error ---
OSError: [Errno 28] No space left on device
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 828, in unpack
data = self.settings["source_path_hash"])
File "/usr/lib64/python3.6/site-packages/catalyst/base/resume.py", line 56, in enable
myf.write(data)
OSError: [Errno 28] No space left on device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/logging/__init__.py", line 998, in emit
self.flush()
File "/usr/lib64/python3.6/logging/__init__.py", line 978, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.6/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 285, in main
return _main(parser, opts)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 452, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 114, in build_target
return target.run()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run
log.error('Exception running action sequence %s', x, exc_info=True)
File "/usr/lib64/python3.6/logging/__init__.py", line 1337, in error
self._log(ERROR, msg, args, **kwargs)
File "/usr/lib64/python3.6/site-packages/catalyst/log.py", line 29, in _log
super(CatalystLogger, self)._log(level, line, (), **kwargs)
Message: 'Exception running action sequence unpack'
Arguments: ()
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib64/python3.6/logging/__init__.py", line 998, in emit
self.flush()
File "/usr/lib64/python3.6/logging/__init__.py", line 978, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.6/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 285, in main
return _main(parser, opts)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 452, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.6/site-packages/catalyst/main.py", line 114, in build_target
return target.run()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stageb
Full build log at /home/release/tmp/run/catalyst-auto.20190614T185156Z.VHU94x/log/stage4-nomultilib-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-06-15 6:32 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-14 18:35 [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-nomultilib-minimal.spec catalyst
-- strict thread matches above, loose matches on Subject: below --
2019-06-15 6:32 catalyst
2019-06-11 9:26 catalyst
2019-06-11 1:30 catalyst
2019-03-02 16:22 catalyst
2019-03-02 16:10 catalyst
2018-08-04 20:33 catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox