timeout option not honoured (formerly how to handle armhf time-out on package?)

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Pjotr Prins
Owner
unassigned
Submitted by
Pjotr Prins
Severity
normal

Debbugs page

P
P
Pjotr Prins wrote on 19 Feb 2018 15:15
(name . Ludovic Courtès)(address . ludo@gnu.org)
20180219231558.GA15863@thebird.nl
the fix did not work, see


est project /tmp/guix-build-ldc-0.17.4.drv-0/build
Start 1: build-druntime-ldc-unittest
1/673 Test #1: build-druntime-ldc-unittest ................. Passed 533.53 sec
Start 2: build-druntime-test-runner
2/673 Test #2: build-druntime-test-runner .................. Passed 6.06 sec
Start 3: build-phobos2-ldc-unittest
building of `/gnu/store/4bqm0has81ndhimqg9nn7kysdzdhssy7-ldc-0.17.4.drv' timed out after 3600 seconds of silence
@ build-failed /gnu/store/4bqm0has81ndhimqg9nn7kysdzdhssy7-ldc-0.17.4.drv - timeout

Strangely no effect on the timeout.

CC debbugs so we don't lose it.

On Fri, Feb 16, 2018 at 10:56:32AM +0100, Ludovic Courtès wrote:
Toggle quote (36 lines)
> Hello,
>
> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>
> > According to
> >
> > https://hydra.gnu.org/build/2447190/nixlog/1/tail-reload
> >
> > we are getting a time-out during testing of dlang ldc on armhf.
> >
> > I admit 3600s for a test is a bit lengthy ;)
>
> Indeed, on x86_64, according to
> <https://mirror.hydra.gnu.org/log/q31z6ncd448p4qdcc9xd2j0c08bwbwff-ldc-0.17.4>, we get:
>
> --8<---------------cut here---------------start------------->8---
> /gnu/store/6g4pfzgmgwpfkwix0p7r6j349hffh2gs-cmake-3.7.2/bin/ctest --force-new-ctest-process
> Test project /tmp/guix-build-ldc-0.17.4.drv-0/build
> Start 1: build-druntime-ldc-unittest
> 1/673 Test #1: build-druntime-ldc-unittest ................. Passed 36.71 sec
> Start 2: build-druntime-test-runner
> 2/673 Test #2: build-druntime-test-runner .................. Passed 0.34 sec
> Start 3: build-phobos2-ldc-unittest
> 3/673 Test #3: build-phobos2-ldc-unittest .................. Passed 487.52 sec
> --8<---------------cut here---------------end--------------->8---
>
> So given that the first test is 14 times slower on x86_64, we can expect
> the 3rd test to last ~8440 seconds, which exceeds the default
> ‘max-silent-timeout’.
>
> I’ve added a ’max-silent-time’ property as Mark suggests, for 3h.
>
> Thanks,
> Ludo’.
>

--
L
L
Ludovic Courtès wrote on 3 Mar 2018 13:22
control message for bug #30541
(address . control@debbugs.gnu.org)
87d10kam79.fsf@gnu.org
reassign 30541 guix
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 30541@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 30541
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch