From: Mathieu Othacehe <othacehe@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 45826@debbugs.gnu.org, guix-sysadmin@gnu.org
Subject: bug#45826: SBCL / Common Lisp packages fail to build on aarch64
Date: Mon, 18 Jan 2021 14:36:39 +0100 [thread overview]
Message-ID: <87czy2pdso.fsf@gnu.org> (raw)
In-Reply-To: <87mtx794oa.fsf@cbaines.net> (Christopher Baines's message of "Sun, 17 Jan 2021 11:35:49 +0000")
Hey Chris,
> The behaviour is configurable, but the default missing inputs hook will
> submit a new build for a missing input, but only if one doesn't already
> exist. Because of this, you don't get the behaviour where some missing
> prerequisite that fails to built is built over and over again, every
> time you try and build a derivation that uses it.
Oh, makes sense, thanks for explaining. I also had a look to Hydra in
that matter. They are breaking a "Build" into "BuildSteps" corresponding
more or less to the build dependencies, or "Inputs" in the
Coordinator. This way they make sure not to submit multiple times a same
build to the workers.
It means that it is also no longer needed to cache build failures I
guess. I think it would be really nice to port this mechanism to
Cuirass.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-01-18 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 21:04 bug#45826: SBCL / Common Lisp packages fail to build on aarch64 Leo Famulari
2021-01-13 21:03 ` Guillaume Le Vaillant
2021-01-13 23:25 ` Leo Famulari
2021-01-16 9:42 ` Guillaume Le Vaillant
2021-01-16 18:58 ` Leo Famulari
2021-01-17 9:29 ` Mathieu Othacehe
2021-01-17 11:35 ` Christopher Baines
2021-01-18 13:36 ` Mathieu Othacehe [this message]
2021-01-17 19:11 ` Leo Famulari
2021-01-17 19:37 ` Efraim Flashner
2021-01-19 13:13 ` Ludovic Courtès
2021-01-19 20:17 ` Leo Famulari
2021-02-01 20:56 ` Ludovic Courtès
2021-02-01 21:13 ` Leo Famulari
2021-02-01 22:03 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czy2pdso.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=45826@debbugs.gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).