Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@××××××××××××××××.name
To: jmbsvicetto@×××××.com, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1.spec
Date: Sat, 02 Mar 2019 16:07:57
Message-Id: 20190302160753.3D66661B9E@thor.jmbsvicetto.name
1 *** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage1.spec
2 02 Mar 2019 16:07:35 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
3 02 Mar 2019 16:07:35 UTC: NOTICE : conf_values[options] = {'bindist', 'clear-autoresume', 'preserve_libs', 'pkgcache'}
4 02 Mar 2019 16:07:35 UTC: NOTICE : Processing spec file: stage1.spec
5 02 Mar 2019 16:07:35 UTC: NOTICE : Using target: stage1
6 02 Mar 2019 16:07:35 UTC: NOTICE : Source file specification matching setting is: loose
7 02 Mar 2019 16:07:35 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
8 02 Mar 2019 16:07:35 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
9 02 Mar 2019 16:07:35 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z/tmp/stage1root
10 02 Mar 2019 16:07:35 UTC: NOTICE : --- Running action sequence: unpack
11 02 Mar 2019 16:07:35 UTC: NOTICE : Clearing the chroot path ...
12 02 Mar 2019 16:07:35 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z
13 02 Mar 2019 16:07:35 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
14 02 Mar 2019 16:07:35 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z (this may take some time) ..
15 02 Mar 2019 16:07:39 UTC: NOTICE : --- Running action sequence: unpack_snapshot
16 02 Mar 2019 16:07:39 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
17 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: setup_confdir
18 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: portage_overlay
19 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: base_dirs
20 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: bind
21 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: chroot_setup
22 02 Mar 2019 16:07:48 UTC: NOTICE : Setting up chroot...
23 02 Mar 2019 16:07:48 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
24 02 Mar 2019 16:07:48 UTC: WARNING : If your build fails look here first as the possible problem.
25 02 Mar 2019 16:07:48 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
26 02 Mar 2019 16:07:48 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
27 02 Mar 2019 16:07:48 UTC: WARNING : You have been warned.
28 02 Mar 2019 16:07:48 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z/etc/portage/make.conf
29 02 Mar 2019 16:07:48 UTC: NOTICE : STICKY-CONFIG is enabled
30 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: setup_environment
31 02 Mar 2019 16:07:48 UTC: NOTICE : --- Running action sequence: run_local
32 copying make.conf to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z/tmp/stage1root/etc/portage
33 Copying stage1-chroot.sh to /tmp
34 copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z/tmp
35 copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z/tmp
36 Ensure the file has the executable bit set
37 Running stage1-chroot.sh in chroot:
38 chroot /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20190302T160623Z /tmp/stage1-chroot.sh
39 >>> Regenerating /etc/ld.so.cache...
40 Adding USE="${USE} build" to make.conf for portage build
41 emerge --quiet --oneshot --update --newuse sys-apps/portage
42
43 Performing Global Updates
44 (Could take a couple of minutes if you have a lot of binary packages.)
45
46
47 * Last emerge --sync was 210d 3h 2m 49s ago.
48 >>> Verifying ebuild manifests
49 >>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
50 >>> Failed to emerge sys-apps/portage-2.3.40-r1, Log file:
51 >>> '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-160751.log'
52 * Package: sys-apps/portage-2.3.40-r1
53 * Repository: gentoo
54 * Maintainer: dev-portage@g.o
55 * Upstream: dev-portage@g.o
56 * 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
57 * FEATURES: preserve-libs sandbox userpriv usersandbox
58 * Please follow the instructions in the news item:
59 * 2017-12-26-experimental-amd64-17-1-profiles
60 * or choose the 17.0 profile.
61 * ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
62 * ERROR: 17.1 migration has not been performed!!
63 *
64 * Call stack:
65 * ebuild.sh, line 610: Called __source_all_bashrcs
66 * ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
67 * ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
68 * profile.bashrc, line 6: Called die
69 * The specific snippet of code:
70 * die "ERROR: 17.1 migration has not been performed!!"
71 *
72 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
73 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
74 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-160751.log'.
75 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
76 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
77 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
78 * S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
79 * Messages for package sys-apps/portage-2.3.40-r1:
80 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-160751.log
81 * Please follow the instructions in the news item:
82 * 2017-12-26-experimental-amd64-17-1-profiles
83 * or choose the 17.0 profile.
84 * ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
85 * ERROR: 17.1 migration has not been performed!!
86 *
87 * Call stack:
88 * ebuild.sh, line 610: Called __source_all_bashrcs
89 * ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
90 * ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
91 * profile.bashrc, line 6: Called die
92 * The specific snippet of code:
93 * die "ERROR: 17.1 migration has not been performed!!"
94 *
95 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
96 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
97 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-160751.log'.
98 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
99 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
100 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
101 * S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
102
103
104 02 Mar 2019 16:07:52 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
105 02 Mar 2019 16:07:53 UTC: ERROR : CatalystError: Stage build aborting due to error.
106 02 Mar 2019 16:07:53 UTC: ERROR : Exception running action sequence run_local
107 Traceback (most recent call last):
108 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
109 env=self.env)
110 File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
111 print_traceback=False)
112 catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
113
114 During handling of the above exception, another exception occurred:
115
116 Traceback (most recent call last):
117 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1455, in run
118 getattr(self, x)()
119 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local
120 print_traceback=False)
121 catalyst.support.CatalystError: Stage build aborting due to error.
122 02 Mar 2019 16:07:53 UTC: NOTICE : Cleaning up... Running unbind()
123 Command exited with non-zero status 2
124 35.47user 3.77system 0:18.25elapsed 214%CPU (0avgtext+0avgdata 359144maxresident)k
125 2136inputs+3860248outputs (0major+507425minor)pagefaults 0swaps
126
127
128
129 Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/stage1.log