From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 29634@debbugs.gnu.org
Subject: bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
Date: Tue, 12 Dec 2017 10:21:08 +0100 [thread overview]
Message-ID: <87po7ks3nf.fsf@gnu.org> (raw)
In-Reply-To: <87y3m8irez.fsf@netris.org> (Mark H. Weaver's message of "Mon, 11 Dec 2017 21:57:56 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> An early 'guile' build on armhf-linux consistently fails on Hydra,
>>> because the 'timeout' and 'max-silent-time' properties are not honored.
>>> For example:
>>>
>>> https://hydra.gnu.org/build/2391845
>>>
>>> This is a longstanding issue. In past core-updates cycles, I have
>>> worked around the problem by rebuilding these early 'guile' derivations
>>> from Hydra's command line, passing --timeout and --max-silent-time
>>> manually, and then restarting the many dependency failures.
>>>
>>> It would be good to fix this issue properly.
>>>
>>> My guess is that the build parameters are not honored because there is
>>> no Hydra 'job' associated with this early 'guile'.
>>
>> Exactly. Or maybe there’s one but this early ‘guile’ is built as a
>> dependency of another job.
>
> How do you think we should fix this?
Of course I’d prefer if Guile compile times were shorter.
Besides, we should probably handle timeouts per-derivation rather than
globally (currently timeout are per-session, see ‘set-build-options’).
We could do that by adding a new special value in the environment
variable map of derivation (as is the case for, e.g.,
“exportReferencesGraph”) that the daemon would honor. It’s a
rebuild-the-world change though.
Ludo’.
next prev parent reply other threads:[~2017-12-12 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 2:02 bug#29634: Hydra fails to honor 'max-silent-time' for early guile build Mark H Weaver
2017-12-11 9:40 ` Ludovic Courtès
2017-12-12 2:57 ` Mark H Weaver
2017-12-12 9:21 ` Ludovic Courtès [this message]
2017-12-12 22:12 ` Mark H Weaver
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=87po7ks3nf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29634@debbugs.gnu.org \
--cc=mhw@netris.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.