From: Christopher Baines <mail@cbaines.net>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org, 48435@debbugs.gnu.org
Subject: Re: Bringing substitutes from the Guix Build Coordinator to users
Date: Wed, 19 May 2021 08:57:56 +0100 [thread overview]
Message-ID: <87fsyjb1ff.fsf@cbaines.net> (raw)
In-Reply-To: <87eee3tdrh.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Mathieu Othacehe <othacehe@gnu.org> writes:
> Hey Chris,
>
>> That sounds sensible. On the specific name, given this is just about
>> substitutes, and at least in my opinion has nothing to do with
>> continuous integration, maybe picking just another word would avoid
>> thinking too much, it could be bordeaux, or hippo, or anything
>> really. As you say, stability and not being tied to a particular machine
>> is the important thing.
>
> The substitutes coverage is one indicator to take into account but there
> are many others. For instance, the evaluation speed, the failed
> evaluation count, the average evaluation builds completion time, the
> availability of the connected build machines between other things.
Indeed, and I'm aware that the Guix Data Service, which performs a
similar function to the evaluations in Cuirass, is much slower.
> Deploying a solution that builds substitutes is fine, but as soon as it
> is deployed and accessible to all Guix users, the system administrators
> will have to monitor it and maintain it in the long run.
>
> Having two heterogeneous build infrastructures on two sets of machines,
> providing different metrics will make the update and maintenance of
> those machines harder.
>
> I hear your point about K-out-of-N policy and it also makes sense to
> me. However, we should maybe consider doing it using two similar
> infrastructures.
Indeed. The reality though is that two different approaches have been in
development now for a little over a year, and this is a reflection of
that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-05-19 7:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 18:56 Bringing substitutes from the Guix Build Coordinator to users Christopher Baines
2021-05-02 21:51 ` Ludovic Courtès
2021-05-03 10:30 ` Christopher Baines
2021-05-04 8:27 ` Ludovic Courtès
2021-05-04 19:22 ` Christopher Baines
2021-05-11 20:18 ` Ludovic Courtès
2021-05-04 18:38 ` Andreas Enge
2021-05-04 19:29 ` Christopher Baines
2021-05-12 22:58 ` Christopher Baines
2021-05-15 16:38 ` Ludovic Courtès
2021-05-15 17:24 ` Christopher Baines
2021-05-17 20:28 ` Ludovic Courtès
2021-05-18 8:26 ` Christopher Baines
2021-05-06 16:26 ` Ludovic Courtès
2021-05-18 19:45 ` [bug#48435] " Christopher Baines
2021-05-18 21:24 ` Ludovic Courtès
2021-05-18 22:29 ` Christopher Baines
2021-05-19 6:54 ` Mathieu Othacehe
2021-05-19 7:57 ` Christopher Baines [this message]
2021-06-07 14:53 ` Christopher Baines
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=87fsyjb1ff.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=48435@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=othacehe@gnu.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.
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).