From: Pierre Langlois <pierre.langlois@gmx.com>
To: 35139@debbugs.gnu.org
Cc: Ivan Petkov <ivanppetkov@gmail.com>
Subject: bug#35139: Rust builds systematically time out
Date: Thu, 04 Apr 2019 10:28:59 +0100 [thread overview]
Message-ID: <87bm1mglus.fsf@gmx.com> (raw)
In-Reply-To: <878swqtabb.fsf@gnu.org>
Hello!
Ludovic Courtès writes:
> Hello,
>
> On berlin, Rust 1.24.1 builds systematically exceed the timeout:
>
> --8<---------------cut here---------------start------------->8---
> Building stage1 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
> Compiling arena v0.0.0 (file:///tmp/guix-build-rust-1.24.1.drv-0/rustc-1.24.1-src/src/libarena)
> Compiling rustc_driver v0.0.0 (file:///tmp/guix-build-rust-1.24.1.drv-0/rustc-1.24.1-src/src/librustc_driver)
>
> [...]
>
> Compiling rls-data v0.14.0
> Compiling rustc_data_structures v0.0.0 (file:///tmp/guix-build-rust-1.24.1.drv-0/rustc-1.24.1-src/src/librustc_data_structures)
> Compiling flate2 v1.0.1
> Compiling syntax_pos v0.0.0 (file:///tmp/guix-build-rust-1.24.1.drv-0/rustc-1.24.1-src/src/libsyntax_pos)
> Compiling rustc_errors v0.0.0 (file:///tmp/guix-build-rust-1.24.1.drv-0/rustc-1.24.1-src/src/librustc_errors)
> Compiling backtrace v0.3.4
> guix offload: error: timeout expired while offloading '/gnu/store/61bd22d9mg3xl260jwddisiahh3kmanj-rust-1.24.1.drv'
> --8<---------------cut here---------------end--------------->8---
>
> Strangely, the build lasts ~9000 seconds (2.5 hours) on the front-end
> node of berlin¹, and the timeout for guix-daemon on berlin is 6h (see
> guix-maintenance.git) while the max-silent-time is 1h.
>
> The build nodes may be slower than the front-end, but still, it seems
> unlikely that it would take more than 6h there. (That could happen if
> the test suite, which lasts 2.1h, were “embarrassingly parallel”, but
> we’re running tests with ‘-j1’.)
>
> To summarize, there are two problems:
>
> 1. Rust takes too long to build. What can we do about it? Enable
> parallel builds?
One thing I suggested in the past was to remove the check phase *only*
for rust packages used for bootstrapping. This way we still run the
tests for the final rust but not at every step in the chain.
Although, I wonder if we're more likely to miss a bug if we do this, I'm
not sure.
For reference: https://lists.gnu.org/archive/html/guix-patches/2018-11/msg00453.html
Thanks,
Pierre
next prev parent reply other threads:[~2019-04-04 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:59 bug#35139: Rust builds systematically time out Ludovic Courtès
2019-04-04 9:28 ` Pierre Langlois [this message]
2019-04-04 15:47 ` Ivan Petkov
2019-04-04 16:06 ` Ludovic Courtès
2019-04-04 17:37 ` Ivan Petkov
2020-12-18 10:29 ` Mathieu Othacehe
2020-12-18 10:45 ` zimoun
2019-04-05 21:18 ` mikadoZero
2020-03-30 5:42 ` John Soo
2021-11-21 6:09 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bm1mglus.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=35139@debbugs.gnu.org \
--cc=ivanppetkov@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).