From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>, guix-patches@gnu.org
Subject: timeout option not honoured (formerly how to handle armhf time-out on package?)
Date: Tue, 20 Feb 2018 00:15:58 +0100 [thread overview]
Message-ID: <20180219231558.GA15863@thebird.nl> (raw)
In-Reply-To: <87tvuhqmun.fsf@gnu.org>
the fix did not work, see
https://hydra.gnu.org/build/2513115
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:
> 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’.
>
--
prev parent reply other threads:[~2018-02-19 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 8:20 How to handle armhf time-out on package? Pjotr Prins
2018-02-16 9:17 ` Mark H Weaver
2018-02-16 9:56 ` Ludovic Courtès
2018-02-19 23:15 ` Pjotr Prins [this message]
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=20180219231558.GA15863@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=guix-patches@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.