From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: librsvg & Rust
Date: Fri, 15 Mar 2019 12:27:41 +0100 [thread overview]
Message-ID: <877ed074ya.fsf@gnu.org> (raw)
In-Reply-To: <20190308031716.438f1573@scratchpost.org> (Danny Milosavljevic's message of "Fri, 8 Mar 2019 03:17:16 +0100")
Hello!
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> http://hydra.gnu.org/build/3385267/nixlog/3/raw seems to be the latest
> armhf-linux build attempt on master and it says:
>
> building of `/gnu/store/xqwkq4hvc3wq7pvx4fcj3sws55zp64b7-rust-1.19.0.drv' timed out after 3600 seconds of silence
>
> However, rust-1.19 on master has:
>
> (properties '((timeout . 72000) ;20 hours
> (max-silent-time . 18000))) ;5 hours (for armel)
>
> Why does it already time out after 3600 seconds of silence although it's configured to stand 18000 seconds of silence?
Note that these properties are ignored by Cuirass, and I believe there
can be cases on Hydra where it’s not honored either (e.g., if
‘rust-1.19’ is built has a dependency of another job.)
Ludo’.
next prev parent reply other threads:[~2019-03-15 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190220161027.17460.87383@vcs0.savannah.gnu.org>
[not found] ` <20190220161038.3F54B2040C@vcs0.savannah.gnu.org>
2019-03-06 11:05 ` librsvg & Rust Ludovic Courtès
2019-03-06 15:46 ` Marius Bakke
2019-03-06 16:24 ` ng0
2019-03-06 23:55 ` Mark H Weaver
2019-03-07 20:12 ` Efraim Flashner
2019-03-08 1:52 ` Danny Milosavljevic
2019-03-08 2:17 ` Danny Milosavljevic
2019-03-15 11:27 ` Ludovic Courtès [this message]
2019-03-15 11:29 ` Ludovic Courtès
2019-03-15 13:39 ` Marius Bakke
2019-03-15 15:14 ` Ivan Petkov
2019-03-23 16:53 ` Ludovic Courtès
2019-03-23 22:44 ` Marius Bakke
2019-04-03 21:30 ` Ludovic Courtès
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=877ed074ya.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.