unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Pierre Neidhardt" <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Missing substitutes and TIMEOUT property (Racket, MAME)
Date: Sun, 15 Mar 2020 17:52:34 +0100	[thread overview]
Message-ID: <87mu8hlfvx.fsf@devup.no> (raw)
In-Reply-To: <87blp1u2kf.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>
>> Some packages are frequently without substitutes, like Racket and MAME.
>> Link between the two?  They both take a long time to build.  So I wonder
>> if this is not because the build somehow timeouts.
>>
>> I see that there is a `timeout' property on packages like chromium,
>> qtwebkit, etc.
>
> Few people know that this property has absolutely no effect.  :-)
>
> It used to be that Hydra would honor it.  But Cuirass has never honored it.
>
> It’s not clear to me whether Cuirass should honor it, in fact.
>
> 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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-03-15 16:52 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 [this message]
2020-03-15 21:41     ` Ludovic Courtès

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=87mu8hlfvx.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).