* bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
@ 2017-12-10 2:02 Mark H Weaver
2017-12-11 9:40 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: Mark H Weaver @ 2017-12-10 2:02 UTC (permalink / raw)
To: 29634
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'.
Mark
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
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
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2017-12-11 9:40 UTC (permalink / raw)
To: Mark H Weaver; +Cc: 29634
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.
Ludo’.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
2017-12-11 9:40 ` Ludovic Courtès
@ 2017-12-12 2:57 ` Mark H Weaver
2017-12-12 9:21 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: Mark H Weaver @ 2017-12-12 2:57 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 29634
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?
Mark
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
2017-12-12 2:57 ` Mark H Weaver
@ 2017-12-12 9:21 ` Ludovic Courtès
2017-12-12 22:12 ` Mark H Weaver
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2017-12-12 9:21 UTC (permalink / raw)
To: Mark H Weaver; +Cc: 29634
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’.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#29634: Hydra fails to honor 'max-silent-time' for early guile build
2017-12-12 9:21 ` Ludovic Courtès
@ 2017-12-12 22:12 ` Mark H Weaver
0 siblings, 0 replies; 5+ messages in thread
From: Mark H Weaver @ 2017-12-12 22:12 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 29634
ludo@gnu.org (Ludovic Courtès) writes:
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-12-12 22:14 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2017-12-12 22:12 ` Mark H Weaver
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.