'max-silent-time' etc. should be per-derivation settings

OpenSubmitted by Mark H Weaver.
Details
2 participants
  • Ludovic Courtès
  • Mark H Weaver
Owner
unassigned
Severity
normal
M
M
Mark H Weaver wrote on 10 Dec 2017 03:02
Hydra fails to honor 'max-silent-time' for early guile build
(address . bug-guix@gnu.org)
87efo3jq65.fsf@netris.org
An early 'guile' build on armhf-linux consistently fails on Hydra,
because the 'timeout' and 'max-silent-time' properties are not honored.
For example:


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

Mark
L
L
Ludovic Courtès wrote on 11 Dec 2017 10:40
(name . Mark H Weaver)(address . mhw@netris.org)(address . 29634@debbugs.gnu.org)
877ett4n7r.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skribis:

Toggle quote (16 lines)
> 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.

Ludo’.
M
M
Mark H Weaver wrote on 12 Dec 2017 03:57
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 29634@debbugs.gnu.org)
87y3m8irez.fsf@netris.org
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (21 lines)
> 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?

Mark
L
L
Ludovic Courtès wrote on 12 Dec 2017 10:21
(name . Mark H Weaver)(address . mhw@netris.org)(address . 29634@debbugs.gnu.org)
87po7ks3nf.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skribis:

Toggle quote (25 lines)
> 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’.
M
M
Mark H Weaver wrote on 12 Dec 2017 23:12
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 29634@debbugs.gnu.org)
87h8svd28n.fsf@netris.org
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (36 lines)
> 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.

Sounds good to me. For now, I'll rebuild the early guile for armhf
manually.

Thanks,
Mark
L
L
Ludovic Courtès wrote on 8 Jan 2018 15:28
control message for bug #29634
(address . control@debbugs.gnu.org)
87d12kfmqw.fsf@gnu.org
retitle 29634 'max-silent-time' etc. should be per-derivation settings
?