public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@milou.amd64.dev.gentoo.org
To: gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst build error - snapshot
Date: Wed, 05 Mar 2025 17:05:01 +0000 (UTC)	[thread overview]
Message-ID: <20250305170501.7E5F07491C4@milou.amd64.dev.gentoo.org> (raw)




*** Running command: catalyst -c /etc/catalyst/catalyst.conf -s stable
05 Mar 2025 17:05:01 UTC: NOTICE  : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
05 Mar 2025 17:05:01 UTC: NOTICE  : conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache']
NOTICE:catalyst:conf_values[options] = ['bindist', 'kerncache', 'pkgcache', 'seedcache']
05 Mar 2025 17:05:01 UTC: NOTICE  : >>> /usr/bin/git -C /var/tmp/catalyst/repos/gentoo.git fetch --quiet --depth=1
NOTICE:catalyst:>>> /usr/bin/git -C /var/tmp/catalyst/repos/gentoo.git fetch --quiet --depth=1
05 Mar 2025 17:05:01 UTC: ERROR   : CatalystError: ['/usr/bin/git', '-C', '/var/tmp/catalyst/repos/gentoo.git', 'fetch', '--quiet', '--depth=1'] failed with return code128
ERROR:catalyst:CatalystError: ['/usr/bin/git', '-C', '/var/tmp/catalyst/repos/gentoo.git', 'fetch', '--quiet', '--depth=1'] failed with return code128
05 Mar 2025 17:05:01 UTC: ERROR   : 
ERROR:catalyst:
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/catalyst/targets/snapshot.py", line 61, in update_ebuild_repo
    subprocess.run(cmd,
  File "/usr/lib/python3.12/subprocess.py", line 573, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/git', '-C', '/var/tmp/catalyst/repos/gentoo.git', 'fetch', '--quiet', '--depth=1']' returned non-zero exit status 128.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.12/catalyst", line 27, in <module>
    main(sys.argv[1:])
  File "/usr/lib/python3.12/site-packages/catalyst/main.py", line 257, in main
    return _main(parser, opts)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/catalyst/main.py", line 367, in _main
    success = build_target(addlargs)
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/catalyst/main.py", line 87, in build_target
    return target.run()
           ^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/catalyst/targets/snapshot.py", line 81, in run
    treeish = self.update_ebuild_repo()
              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/catalyst/targets/snapshot.py", line 75, in update_ebuild_repo
    raise CatalystError(f'{e.cmd} failed with return code'
catalyst.support.CatalystError: ['/usr/bin/git', '-C', '/var/tmp/catalyst/repos/gentoo.git', 'fetch', '--quiet', '--depth=1'] failed with return code128





Full build log at /tmp/tmp.2nPdsSWEwF


             reply	other threads:[~2025-03-05 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 17:05 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-19 17:05 [gentoo-releng-autobuilds] [m68k-qemu-auto] Catalyst build error - snapshot 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=20250305170501.7E5F07491C4@milou.amd64.dev.gentoo.org \
    --to=catalyst@milou.amd64.dev.gentoo.org \
    --cc=gentoo-releng-autobuilds@lists.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