From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Missing substitutes and TIMEOUT property (Racket, MAME)
Date: Sun, 15 Mar 2020 22:41:10 +0100 [thread overview]
Message-ID: <87eettgutl.fsf@gnu.org> (raw)
In-Reply-To: <87mu8hlfvx.fsf@devup.no> (Marius Bakke's message of "Sun, 15 Mar 2020 17:52:34 +0100")
Hi,
Marius Bakke <mbakke@fastmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> At the Guix level, timeouts are per session: you set them for all your
>> session with ‘set-build-options’. So if you want them per-derivation,
>> you basically need to create one session per derivation build; that’s
>> what Hydra did.
>>
>> But there’s a good reason for it to be per-session: the admin may want
>> to be in control of those parameters. For example, on berlin, we’d
>> rather make sure machines don’t stay idle for too long.
>
> Maybe we could create a separate jobset for the jobs that require a
> longer max-silent-time, IIUC?
Not really, because Cuirass does not use per-jobset sessions.
So really, we’d have to change the timeouts globally for guix-daemon, or
for all of Cuirass.
Perhaps we should start by creating a list of affected package/system
pairs, and from there we could make a more informed decisions.
Thoughts?
Ludo’.
prev parent reply other threads:[~2020-03-15 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:58 Missing substitutes and TIMEOUT property (Racket, MAME) Pierre Neidhardt
2020-03-02 11:50 ` Pierre Neidhardt
2020-03-02 17:29 ` Leo Famulari
2020-03-03 9:42 ` Pierre Neidhardt
2020-03-03 13:48 ` Tobias Geerinckx-Rice
2020-03-03 14:09 ` Pierre Neidhardt
2020-03-03 14:35 ` Tobias Geerinckx-Rice
2020-03-03 17:01 ` Gábor Boskovits
2020-03-04 14:17 ` Pierre Neidhardt
2020-03-12 13:26 ` Ludovic Courtès
2020-03-12 13:45 ` Pierre Neidhardt
2020-03-15 16:52 ` Marius Bakke
2020-03-15 21:41 ` Ludovic Courtès [this message]
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=87eettgutl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.