[gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-nomultilib.spec

*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-nomultilib.spec
11 Jun 2019 01:34:04 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 01:34:04 UTC: NOTICE  : conf_values[options] = {'clear-autoresume', 'bindist', 'pkgcache', 'preserve_libs'}
11 Jun 2019 01:34:04 UTC: NOTICE  : Processing spec file: hardened/stage1-nomultilib.spec
11 Jun 2019 01:34:04 UTC: NOTICE  : Using target: stage1
11 Jun 2019 01:34:04 UTC: NOTICE  : Source file specification matching setting is: loose
11 Jun 2019 01:34:04 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 01:34:05 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
11 Jun 2019 01:34:05 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z/tmp/stage1root
11 Jun 2019 01:34:05 UTC: NOTICE  : --- Running action sequence: unpack
11 Jun 2019 01:34:05 UTC: NOTICE  : Clearing the chroot path ...
11 Jun 2019 01:34:05 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z
11 Jun 2019 01:34:05 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
11 Jun 2019 01:34:05 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z (this may take some time) ..
11 Jun 2019 01:34:08 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
11 Jun 2019 01:34:08 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: setup_confdir
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: portage_overlay
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: base_dirs
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: bind
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: chroot_setup
11 Jun 2019 01:34:18 UTC: NOTICE  : Setting up chroot...
11 Jun 2019 01:34:18 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
11 Jun 2019 01:34:18 UTC: WARNING : If your build fails look here first as the possible problem.
11 Jun 2019 01:34:18 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
11 Jun 2019 01:34:18 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
11 Jun 2019 01:34:18 UTC: WARNING : You have been warned.
11 Jun 2019 01:34:18 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z/etc/portage/make.conf
11 Jun 2019 01:34:18 UTC: NOTICE  : STICKY-CONFIG is enabled
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: setup_environment
11 Jun 2019 01:34:18 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20190611T012607Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --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-013422.log'
 * Package:    sys-apps/portage-2.3.62-r2
 * Repository: gentoo
 * Maintainer: dev-portage@g.o
 * Upstream:   dev-portage@g.o
 * USE:        abi_x86_64 amd64 build 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-013422.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-013421.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-013422.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-013422.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:34:23 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
11 Jun 2019 01:34:23 UTC: ERROR   : CatalystError: Stage build aborting due to error.
11 Jun 2019 01:34:23 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
    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/stage1/stage1-controller.sh', 'run']) 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 1369, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
11 Jun 2019 01:34:23 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
32.44user 4.15system 0:18.51elapsed 197%CPU (0avgtext+0avgdata 351852maxresident)k
16inputs+3712840outputs (0major+614177minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/hardened_stage1-nomultilib.log