all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 44559@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
	Carl Dong <contact@carldong.me>
Subject: bug#44559:
Date: Tue, 23 Feb 2021 09:41:12 +0100	[thread overview]
Message-ID: <87o8gb6us7.fsf@gnu.org> (raw)
In-Reply-To: <875z2jn30q.fsf@cbaines.net> (Christopher Baines's message of "Mon, 22 Feb 2021 22:36:37 +0000")

Hi,

Christopher Baines <mail@cbaines.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Perhaps we could start by testing this hypothesis on a separate build
>> farm.  Chris, Mathieu, WDYT?
>
> I'm currently thinking about attempting these kind of things (testing
> building derivations under different conditions) through the agent tags
> in the Guix Build Coordinator.
>
> I haven't used this functionality yet, but it's mostly implemented. The
> idea is that agents have tags, that describe various attributes that are
> important (time=normal, time=future, maybe for example), and builds can
> also be targeted at specific agents by tagging the builds with those
> same tags.

Sounds nice!  Also varying kernels I guess.

> Where I'm going with this is that I'm not sure a separate build farm is
> needed, it would be good to just incorperate this in to the build farm
> used for testing patches and non-master branches.

Sure.  For the build-in-the-future thing, I think we could just do that
by default; what I meant is that we just need to double-check beforehand
that nothing breaks badly.

Thanks,
Ludo’.




  reply	other threads:[~2021-02-23  8:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 20:49 bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Christopher Baines
2020-11-12 21:06 ` Ludovic Courtès
2020-11-12 21:18   ` Marius Bakke
2020-11-15 11:05     ` Ludovic Courtès
2020-12-31  0:27 ` bug#44559: Solution jeremiah
2021-02-16 21:00 ` bug#44559: Carl Dong
2021-02-16 21:49   ` bug#44559: Leo Famulari
2021-02-19 15:33   ` bug#44559: Ludovic Courtès
2021-02-19 18:32     ` bug#44559: Maxime Devos
2021-02-20 13:46       ` bug#44559: Ludovic Courtès
2021-02-20 14:12         ` bug#44559: Detecting “expiring” builds Ludovic Courtès
2021-02-19 23:49     ` bug#44559: Carl Dong
2021-02-22 22:36     ` bug#44559: Christopher Baines
2021-02-23  8:41       ` Ludovic Courtès [this message]
2021-02-23  8:55         ` bug#44559: Christopher Baines
2022-07-13 15:03         ` bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Maxim Cournoyer
2022-07-15 13:17           ` Ludovic Courtès
2022-07-16  1:33             ` Maxim Cournoyer

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=87o8gb6us7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=44559@debbugs.gnu.org \
    --cc=contact@carldong.me \
    --cc=mail@cbaines.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.