public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@milou.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [aarch64_be-auto] Catalyst fatal build error - stage1-systemd-23.spec
Date: Sat, 19 Oct 2024 17:25:36 +0000 (UTC)	[thread overview]
Message-ID: <20241019172536.A81CC7491B4@milou.amd64.dev.gentoo.org> (raw)




*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20241019T170324Z.av0ktc/specs/stage1-systemd-23.spec
19 Oct 2024 17:15:44 UTC: NOTICE  : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
19 Oct 2024 17:15:44 UTC: NOTICE  : conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache', 'clear-autoresume']
19 Oct 2024 17:15:44 UTC: NOTICE  : Processing spec file: /tmp/catalyst-auto.20241019T170324Z.av0ktc/specs/stage1-systemd-23.spec
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20241019T170324Z.av0ktc/specs/stage1-systemd-23.spec
19 Oct 2024 17:15:44 UTC: NOTICE  : Using target: stage1
NOTICE:catalyst:Using target: stage1
19 Oct 2024 17:15:44 UTC: NOTICE  : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
NOTICE:catalyst:Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
19 Oct 2024 17:15:44 UTC: NOTICE  : Source path set to /var/tmp/catalyst/builds/23.0-default/stage3-aarch64_be-systemd-latest.tar.xz
NOTICE:catalyst:Source path set to /var/tmp/catalyst/builds/23.0-default/stage3-aarch64_be-systemd-latest.tar.xz
19 Oct 2024 17:15:44 UTC: NOTICE  : --- Running action sequence: unpack
NOTICE:catalyst:--- Running action sequence: unpack
19 Oct 2024 17:15:44 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...
19 Oct 2024 17:15:44 UTC: NOTICE  : Clearing the chroot path ...
NOTICE:catalyst:Clearing the chroot path ...
19 Oct 2024 17:15:44 UTC: NOTICE  : Starting auto from /var/tmp/catalyst/builds/23.0-default/stage3-aarch64_be-systemd-latest.tar.xz
NOTICE:catalyst:Starting auto from /var/tmp/catalyst/builds/23.0-default/stage3-aarch64_be-systemd-latest.tar.xz
19 Oct 2024 17:15:44 UTC: NOTICE  : to /var/tmp/catalyst/tmp/23.0-default/stage1-aarch64_be-systemd-20241019T170324Z (this may take some time) ..
NOTICE:catalyst:to /var/tmp/catalyst/tmp/23.0-default/stage1-aarch64_be-systemd-20241019T170324Z (this may take some time) ..
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: config_profile_link
NOTICE:catalyst:--- Running action sequence: config_profile_link
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: setup_confdir
NOTICE:catalyst:--- Running action sequence: setup_confdir
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: process_repos
NOTICE:catalyst:--- Running action sequence: process_repos
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: bind
NOTICE:catalyst:--- Running action sequence: bind
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: chroot_setup
NOTICE:catalyst:--- Running action sequence: chroot_setup
19 Oct 2024 17:15:46 UTC: NOTICE  : Setting up chroot...
NOTICE:catalyst:Setting up chroot...
19 Oct 2024 17:15:46 UTC: NOTICE  : Copying binary interpreter /usr/bin/qemu-aarch64_be into chroot
NOTICE:catalyst:Copying binary interpreter /usr/bin/qemu-aarch64_be into chroot
19 Oct 2024 17:15:46 UTC: WARNING : env variables in catalystrc may cause catastrophic failure.
WARNING:catalyst:env variables in catalystrc may cause catastrophic failure.
19 Oct 2024 17:15:46 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.
19 Oct 2024 17:15:46 UTC: NOTICE  : Writing the stage make.conf to: /var/tmp/catalyst/tmp/23.0-default/stage1-aarch64_be-systemd-20241019T170324Z/etc/portage/make.conf
NOTICE:catalyst:Writing the stage make.conf to: /var/tmp/catalyst/tmp/23.0-default/stage1-aarch64_be-systemd-20241019T170324Z/etc/portage/make.conf
19 Oct 2024 17:15:46 UTC: NOTICE  : STICKY-CONFIG is enabled
NOTICE:catalyst:STICKY-CONFIG is enabled
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: setup_environment
NOTICE:catalyst:--- Running action sequence: setup_environment
19 Oct 2024 17:15:46 UTC: NOTICE  : --- Running action sequence: run_local
NOTICE:catalyst:--- Running action sequence: run_local
Running chroot.sh in chroot:
    chroot /var/tmp/catalyst/tmp/23.0-default/stage1-aarch64_be-systemd-20241019T170324Z /tmp/chroot.sh
>>> Regenerating /etc/ld.so.cache...
Updating seed stage...
emerge --quiet --jobs 10 --load-average 64.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
>>> Emerging (1 of 3) net-libs/libtirpc-1.3.5::gentoo
>>> Installing (1 of 3) net-libs/libtirpc-1.3.5::gentoo
>>> Completed (1 of 3) net-libs/libtirpc-1.3.5::gentoo
>>> Emerging (2 of 3) sys-apps/texinfo-7.1.1::gentoo
>>> Installing (2 of 3) sys-apps/texinfo-7.1.1::gentoo
>>> Completed (2 of 3) sys-apps/texinfo-7.1.1::gentoo
>>> Emerging (3 of 3) net-libs/gnutls-3.8.7.1-r1::gentoo
>>> Failed to emerge net-libs/gnutls-3.8.7.1-r1, Log file:
>>>  '/var/log/portage/net-libs:gnutls-3.8.7.1-r1:20241019-172505.log'
^[[32m * ^[[39;49;00mPackage:    net-libs/gnutls-3.8.7.1-r1:0/30.30
^[[32m * ^[[39;49;00mRepository: gentoo
^[[32m * ^[[39;49;00mMaintainer: base-system@gentoo.org
^[[32m * ^[[39;49;00mUSE:        arm64 cxx elibc_glibc idn kernel_linux nls openssl seccomp tls-heartbeat zlib
^[[32m * ^[[39;49;00mFEATURES:   preserve-libs sandbox userpriv usersandbox
 ^[[32m*^[[0m Applying gnutls-3.8.7.1-configure-brotli.patch ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32m*^[[0m Applying gnutls-3.8.7.1-tests.patch ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32m*^[[0m Running eautoreconf in '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/work/gnutls-3.8.7' ...
 ^[[32m*^[[0m Running 'autopoint --force' ...
^[[A^[[72C ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m

 ^[[31;01m*^[[0m Failed running 'autopoint'!
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m Include in your bug report the contents of:
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m   /var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/autopoint.out

 ^[[31;01m*^[[0m ERROR: net-libs/gnutls-3.8.7.1-r1::gentoo failed (prepare phase):
 ^[[31;01m*^[[0m   Failed running 'autopoint'!
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m     ebuild.sh, line  136:  Called src_prepare
 ^[[31;01m*^[[0m   environment, line 2108:  Called eautoreconf
 ^[[31;01m*^[[0m   environment, line  973:  Called autotools_run_tool '--at-missing' 'autopoint' '--force'
 ^[[31;01m*^[[0m   environment, line  683:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m           die "Failed running '${1}'!";
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=net-libs/gnutls-3.8.7.1-r1::gentoo'`,
 ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=net-libs/gnutls-3.8.7.1-r1::gentoo'`.
 ^[[31;01m*^[[0m The complete build log is located at '/var/log/portage/net-libs:gnutls-3.8.7.1-r1:20241019-172505.log'.
 ^[[31;01m*^[[0m For convenience, a symlink to the build log is located at '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/environment'.
 ^[[31;01m*^[[0m Working directory: '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/work/gnutls-3.8.7'
 ^[[31;01m*^[[0m S: '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/work/gnutls-3.8.7'
 * Messages for package net-libs/gnutls-3.8.7.1-r1:
 * Log file: /var/log/portage/net-libs:gnutls-3.8.7.1-r1:20241019-172505.log
 * Failed running 'autopoint'!
 * 
 * Include in your bug report the contents of:
 * 
 *   /var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/autopoint.out
 * ERROR: net-libs/gnutls-3.8.7.1-r1::gentoo failed (prepare phase):
 *   Failed running 'autopoint'!
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called src_prepare
 *   environment, line 2108:  Called eautoreconf
 *   environment, line  973:  Called autotools_run_tool '--at-missing' 'autopoint' '--force'
 *   environment, line  683:  Called die
 * The specific snippet of code:
 *           die "Failed running '${1}'!";
 * 
 * If you need support, post the output of `emerge --info '=net-libs/gnutls-3.8.7.1-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=net-libs/gnutls-3.8.7.1-r1::gentoo'`.
 * The complete build log is located at '/var/log/portage/net-libs:gnutls-3.8.7.1-r1:20241019-172505.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/work/gnutls-3.8.7'
 * S: '/var/tmp/portage/net-libs/gnutls-3.8.7.1-r1/work/gnutls-3.8.7'


19 Oct 2024 17:25:36 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
19 Oct 2024 17:25:36 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
    func()
  File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 1481, in run_local
    cmd([self.settings['controller_file'], 'run'],
  File "/usr/lib/python3.12/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.12/site-packages/catalyst/base/stagebase.py", line 38, in run_sequence
    func()
  File "/usr/lib/python3.12/site-packages/catalyst/base/stagebase.py", line 1481, in run_local
    cmd([self.settings['controller_file'], 'run'],
  File "/usr/lib/python3.12/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
879.18user 69.11system 9:52.68elapsed 160%CPU (0avgtext+0avgdata 1145600maxresident)k
384684inputs+2205472outputs (85major+23266385minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20241019T170324Z.av0ktc/log/stage1-systemd-23.log


             reply	other threads:[~2024-10-19 17:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 17:25 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-23  4:50 [gentoo-releng-autobuilds] [aarch64_be-auto] Catalyst fatal build error - stage1-systemd-23.spec catalyst
2025-03-16  6:53 catalyst
2025-03-01 23:40 catalyst
2025-02-16  0:16 catalyst
2025-02-08 21:30 catalyst
2025-02-01 21:25 catalyst
2025-01-25 21:46 catalyst
2025-01-22  2:38 catalyst
2025-01-18 17:06 catalyst
2025-01-11 17:05 catalyst
2025-01-04 17:05 catalyst
2024-12-28 17:05 catalyst
2024-12-21 17:05 catalyst
2024-12-14 17:05 catalyst
2024-12-07 17:05 catalyst
2024-11-30 17:05 catalyst
2024-11-23 17:05 catalyst
2024-11-16 17:05 catalyst
2024-11-09 17:05 catalyst
2024-11-02 19:21 catalyst
2024-10-26 17:30 catalyst
2024-09-14 17:05 catalyst
2024-03-24  0:06 catalyst
2024-03-03 15:08 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=20241019172536.A81CC7491B4@milou.amd64.dev.gentoo.org \
    --to=catalyst@milou.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