From: catalyst@timberdoodle.ppc64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ppc-auto] Catalyst fatal build error - ppc32/stage1-openrc.spec
Date: Thu, 17 Feb 2022 00:00:39 +0000 [thread overview]
Message-ID: <20220217000041.2D3D4E0876@pigeon.gentoo.org> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20220217T000036Z.Pr9gcY/specs/ppc32/stage1-openrc.spec
17 Feb 2022 00:00:39 UTC: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
17 Feb 2022 00:00:39 UTC: NOTICE : conf_values[options] = ['autoresume', 'bindist', 'pkgcache', 'seedcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['autoresume', 'bindist', 'pkgcache', 'seedcache', 'clear-autoresume']
17 Feb 2022 00:00:39 UTC: NOTICE : Processing spec file: /tmp/catalyst-auto.20220217T000036Z.Pr9gcY/specs/ppc32/stage1-openrc.spec
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20220217T000036Z.Pr9gcY/specs/ppc32/stage1-openrc.spec
17 Feb 2022 00:00:39 UTC: ERROR : CatalystError: Argument "snapshot" not recognized.
ERROR:catalyst:CatalystError: Argument "snapshot" not recognized.
17 Feb 2022 00:00:39 UTC: ERROR : Also: Required argument "snapshot_treeish" not specified.
ERROR:catalyst: Also: Required argument "snapshot_treeish" not specified.
Command exited with non-zero status 2
0.98user 0.07system 0:01.06elapsed 98%CPU (0avgtext+0avgdata 30060maxresident)k
264inputs+0outputs (0major+12091minor)pagefaults 0swaps
Full build log at /tmp/catalyst-auto.20220217T000036Z.Pr9gcY/log/ppc32_stage1-openrc.log
next reply other threads:[~2022-02-17 0:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 0:00 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-17 4:05 [gentoo-releng-autobuilds] [ppc-auto] Catalyst fatal build error - ppc32/stage1-openrc.spec catalyst
2022-06-13 0:04 catalyst
2022-06-07 0:00 catalyst
2022-06-04 0:03 catalyst
2022-05-30 0:00 catalyst
2022-05-26 0:03 catalyst
2022-05-22 0:00 catalyst
2022-05-17 0:04 catalyst
2022-05-08 0:03 catalyst
2022-04-29 0:03 catalyst
2022-04-28 0:06 catalyst
2022-04-06 0:00 catalyst
2022-01-30 0:00 catalyst
2022-01-04 0:00 catalyst
2021-12-27 0:00 catalyst
2021-12-18 0:00 catalyst
2021-12-04 0:00 catalyst
2021-12-03 0:00 catalyst
2021-11-30 0:00 catalyst
2021-11-16 0:01 catalyst
2021-10-25 0:00 catalyst
2021-10-15 0:00 catalyst
2021-10-14 0:02 catalyst
2021-10-13 0:02 catalyst
2021-10-05 0:00 catalyst
2021-09-25 0:00 catalyst
2021-09-10 0:00 catalyst
2021-08-25 0:00 catalyst
2021-08-17 0:00 catalyst
2021-08-14 0:00 catalyst
2021-08-12 0:00 catalyst
2021-08-11 0:00 catalyst
2021-07-28 0:04 catalyst
2021-07-27 3:08 catalyst
2021-07-22 18:31 catalyst
2021-07-22 0:01 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=20220217000041.2D3D4E0876@pigeon.gentoo.org \
--to=catalyst@timberdoodle.ppc64.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