From: catalyst@demeter.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [riscv-qemu-auto] Catalyst fatal build error - stage1-lp64-musl.spec
Date: Sun, 8 Jan 2023 06:22:47 +0000 (UTC) [thread overview]
Message-ID: <20230108062247.2DB6C268078@demeter.amd64.dev.gentoo.org> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec
08 Jan 2023 05:05:25 UTC: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
08 Jan 2023 05:05:25 UTC: NOTICE : conf_values[options] = ['bindist', 'pkgcache', 'seedcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['bindist', 'pkgcache', 'seedcache', 'clear-autoresume']
08 Jan 2023 05:05:25 UTC: NOTICE : Processing spec file: /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20230106T170214Z.SHiAvp/specs/stage1-lp64-musl.spec
08 Jan 2023 05:05:25 UTC: NOTICE : Using target: stage1
NOTICE:catalyst:Using target: stage1
08 Jan 2023 05:05:25 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2']
NOTICE:catalyst:Accepted source file extensions search order: ['tar.xz', 'xz', 'tar.bz2', 'bz2', 'tbz2']
08 Jan 2023 05:05:25 UTC: NOTICE : Source path set to /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz
NOTICE:catalyst:Source path set to /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz
08 Jan 2023 05:05:25 UTC: NOTICE : --- Running action sequence: unpack
NOTICE:catalyst:--- Running action sequence: unpack
08 Jan 2023 05:05:25 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
NOTICE:catalyst:Referenced SEEDCACHE does not appear to be a directory, trying to untar...
08 Jan 2023 05:05:25 UTC: NOTICE : Clearing the chroot path ...
NOTICE:catalyst:Clearing the chroot path ...
08 Jan 2023 05:05:25 UTC: NOTICE : Starting auto from /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz
NOTICE:catalyst:Starting auto from /var/tmp/catalyst/builds/musl/stage3-rv64_lp64_musl-latest.tar.xz
08 Jan 2023 05:05:25 UTC: NOTICE : to /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z (this may take some time) ..
NOTICE:catalyst:to /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z (this may take some time) ..
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: config_profile_link
NOTICE:catalyst:--- Running action sequence: config_profile_link
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: setup_confdir
NOTICE:catalyst:--- Running action sequence: setup_confdir
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: process_repos
NOTICE:catalyst:--- Running action sequence: process_repos
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: bind
NOTICE:catalyst:--- Running action sequence: bind
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: chroot_setup
NOTICE:catalyst:--- Running action sequence: chroot_setup
08 Jan 2023 05:05:34 UTC: NOTICE : Setting up chroot...
NOTICE:catalyst:Setting up chroot...
08 Jan 2023 05:05:34 UTC: NOTICE : Copying binary interpreter /usr/bin/qemu-riscv64 into chroot
NOTICE:catalyst:Copying binary interpreter /usr/bin/qemu-riscv64 into chroot
08 Jan 2023 05:05:34 UTC: WARNING : env variables in catalystrc may cause catastrophic failure.
WARNING:catalyst:env variables in catalystrc may cause catastrophic failure.
08 Jan 2023 05:05:34 UTC: WARNING : If your build fails look here first as the possible problem.
WARNING:catalyst:If your build fails look here first as the possible problem.
08 Jan 2023 05:05:34 UTC: NOTICE : Writing the stage make.conf to: /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z/etc/portage/make.conf
NOTICE:catalyst:Writing the stage make.conf to: /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z/etc/portage/make.conf
08 Jan 2023 05:05:34 UTC: NOTICE : STICKY-CONFIG is enabled
NOTICE:catalyst:STICKY-CONFIG is enabled
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: setup_environment
NOTICE:catalyst:--- Running action sequence: setup_environment
08 Jan 2023 05:05:34 UTC: NOTICE : --- Running action sequence: run_local
NOTICE:catalyst:--- Running action sequence: run_local
Running chroot.sh in chroot:
chroot /var/tmp/catalyst/tmp/musl/stage1-rv64_lp64_musl-20230106T170214Z /tmp/chroot.sh
>>> Regenerating /etc/ld.so.cache...
Updating seed stage...
emerge --quiet --jobs 10 --load-average 32.0 --buildpkg=n -uDN @world
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Verifying ebuild manifests
>>> Running pre-merge checks for net-misc/openssh-9.1_p1-r2
>>> Running pre-merge checks for sys-apps/portage-3.0.43
* 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 20) sys-libs/ncurses-6.4::gentoo
>>> Emerging (2 of 20) sys-devel/gcc-config-2.10::gentoo
>>> Emerging (3 of 20) sys-devel/binutils-config-5.5::gentoo
>>> Installing (2 of 20) sys-devel/gcc-config-2.10::gentoo
>>> Installing (3 of 20) sys-devel/binutils-config-5.5::gentoo
>>> Installing (1 of 20) sys-libs/ncurses-6.4::gentoo
>>> Emerging (4 of 20) app-alternatives/sh-0::gentoo
>>> Emerging (5 of 20) sys-apps/file-5.44-r1::gentoo
>>> Installing (4 of 20) app-alternatives/sh-0::gentoo
>>> Installing (5 of 20) sys-apps/file-5.44-r1::gentoo
>>> Emerging (6 of 20) dev-db/sqlite-3.40.1::gentoo
>>> Installing (6 of 20) dev-db/sqlite-3.40.1::gentoo
>>> Emerging (7 of 20) sys-apps/kmod-30-r1::gentoo
>>> Emerging (8 of 20) sys-apps/texinfo-7.0.1-r1::gentoo
>>> Installing (8 of 20) sys-apps/texinfo-7.0.1-r1::gentoo
>>> Installing (7 of 20) sys-apps/kmod-30-r1::gentoo
>>> Emerging (9 of 20) net-misc/openssh-9.1_p1-r2::gentoo
>>> Emerging (10 of 20) app-misc/ca-certificates-20211016.3.87::gentoo
>>> Installing (10 of 20) app-misc/ca-certificates-20211016.3.87::gentoo
>>> Installing (9 of 20) net-misc/openssh-9.1_p1-r2::gentoo
>>> Emerging (11 of 20) sys-fs/e2fsprogs-1.46.5-r4::gentoo
>>> Emerging (12 of 20) dev-python/typing-extensions-4.4.0::gentoo
>>> Installing (12 of 20) dev-python/typing-extensions-4.4.0::gentoo
>>> Installing (11 of 20) sys-fs/e2fsprogs-1.46.5-r4::gentoo
>>> Emerging (13 of 20) dev-util/meson-1.0.0::gentoo
>>> Installing (13 of 20) dev-util/meson-1.0.0::gentoo
>>> Emerging (14 of 20) dev-python/cython-0.29.33::gentoo
>>> Installing (14 of 20) dev-python/cython-0.29.33::gentoo
>>> Emerging (15 of 20) app-misc/pax-utils-1.3.6::gentoo
>>> Installing (15 of 20) app-misc/pax-utils-1.3.6::gentoo
>>> Emerging (16 of 20) dev-python/pydantic-1.10.4::gentoo
>>> Installing (16 of 20) dev-python/pydantic-1.10.4::gentoo
>>> Emerging (17 of 20) sys-apps/sandbox-2.30-r1::gentoo
>>> Installing (17 of 20) sys-apps/sandbox-2.30-r1::gentoo
>>> Failed to execute postinst for sys-apps/sandbox-2.30-r1, Log file:
>>> '/var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log'
>>> Emerging (18 of 20) sys-apps/portage-3.0.43::gentoo
>>> Failed to emerge sys-apps/portage-3.0.43, Log file:
>>> '/var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log'
* Messages for package sys-apps/portage-3.0.43:
* Log file: /var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-050618.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 app-alternatives/sh-0:
* Log file: /var/tmp/catalyst/log/app-alternatives:sh-0:20230108-053228.log
* This package will overwrite one or more files that may belong to other
* packages (see list below).
*
* Detected file collision(s):
*
* /bin/sh
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'app-alternatives/sh-0' merged despite file collisions. If
* necessary, refer to your elog messages for the whole content of the
* above message.
* Messages for package sys-apps/sandbox-2.30-r1:
* Log file: /var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log
* The ebuild phase 'postinst' 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.
* FAILED postinst: 1
* The ebuild phase 'other' 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-apps/portage-3.0.43:
* Log file: /var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* 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.
*
* The following 2 packages have failed to build, install, or execute
* postinst:
*
* (sys-apps/sandbox-2.30-r1:0/0::gentoo, ebuild scheduled for merge) (postinst failed), Log file:
* '/var/tmp/catalyst/log/sys-apps:sandbox-2.30-r1:20230108-062013.log'
* (sys-apps/portage-3.0.43:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/catalyst/log/sys-apps:portage-3.0.43:20230108-062242.log'
*
08 Jan 2023 06:22:47 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
08 Jan 2023 06:22:47 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
func()
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 1380, in run_local
cmd([self.settings['controller_file'], 'run'],
File "/usr/lib/python3.10/site-packages/catalyst/support.py", line 66, in cmd
raise CatalystError('cmd(%r) exited %s' % (args, ret),
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
ERROR:catalyst:Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
func()
File "/usr/lib/python3.10/site-packages/catalyst/base/stagebase.py", line 1380, in run_local
cmd([self.settings['controller_file'], 'run'],
File "/usr/lib/python3.10/site-packages/catalyst/support.py", line 66, in cmd
raise CatalystError('cmd(%r) exited %s' % (args, ret),
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/controller.sh', 'run']) exited 1
Command exited with non-zero status 2
10860.36user 513.57system 1:17:22elapsed 245%CPU (0avgtext+0avgdata 530108maxresident)k
478792inputs+2144232outputs (394major+216953199minor)pagefaults 0swaps
Full build log at /tmp/catalyst-auto.20230106T170214Z.SHiAvp/log/stage1-lp64-musl.log
next reply other threads:[~2023-01-08 6:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 6:22 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-11 18:34 [gentoo-releng-autobuilds] [riscv-qemu-auto] Catalyst fatal build error - stage1-lp64-musl.spec catalyst
2024-02-07 1:33 catalyst
2023-07-08 16:47 catalyst
2023-06-07 6:48 catalyst
2023-05-06 22:57 catalyst
2023-02-18 23:56 catalyst
2023-01-14 15:47 catalyst
2022-12-15 14:06 catalyst
2022-11-26 4:42 catalyst
2022-11-18 23:30 catalyst
2022-11-12 15:58 catalyst
2022-11-06 6:13 catalyst
2022-10-01 1:50 catalyst
2022-09-24 15:22 catalyst
2022-09-17 13:11 catalyst
2022-09-10 23:40 catalyst
2022-09-03 2:00 catalyst
2022-08-27 7:10 catalyst
2022-08-21 5:19 catalyst
2022-08-13 17:54 catalyst
2022-08-12 4:26 catalyst
2022-08-10 2:59 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230108062247.2DB6C268078@demeter.amd64.dev.gentoo.org \
--to=catalyst@demeter.amd64.dev.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox