all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Missing substitutes and TIMEOUT property (Racket, MAME)
Date: Thu, 12 Mar 2020 14:45:06 +0100	[thread overview]
Message-ID: <87r1xxhel9.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87blp1u2kf.fsf@gnu.org>

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

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

> 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.

This makes sense, but for now it seems that it's hard to know whether
the build failed because of a timeout or something else.
I suppose some improvements should be done on the Cuirass / Data service
fronts.

If we confirm that timeouts really cause the issue, then I suppose the Berlin
admin can increase the timeout so that the offending packages build.

Thoughts?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2020-03-12 13:45 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 [this message]
2020-03-15 16:52   ` Marius Bakke
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1xxhel9.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.