From: Ivan Petkov <ivanppetkov@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35139@debbugs.gnu.org
Subject: bug#35139: Rust builds systematically time out
Date: Thu, 4 Apr 2019 10:37:03 -0700 [thread overview]
Message-ID: <17B412D1-5D9A-40C8-B37E-D8C08F0E9641@gmail.com> (raw)
In-Reply-To: <87imvtrc0g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
Danny’s got a patch for turning on parallel tests in #35126
Not sure why the previous tests were running sequentially, but there is a comment somewhere saying it’s to avoid EAGAIN errors.
--Ivan
> On Apr 4, 2019, at 9:06 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Ivan Petkov <ivanppetkov@gmail.com> skribis:
>
>>> On Apr 4, 2019, at 1:59 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>>>
>>> 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?
>>
>> Rust tests are designed to run in parallel, as long as you have enough
>> RAM, file descriptors, etc. available on the machine for the amount of
>> concurrency being used. The compiler test suite is largely just compiling
>> files, so the most important resource is probably available RAM/swap.
>
> Perhaps we could start with:
>
> "-j" (number->string (min (parallel-job-count) 2))
>
> ?
>
>> Maybe if the bootstrapped versions don’t ever change skipping the check
>> phase will be safe, but I think we should try running parallel tests first
>> and see how far that gets us.
>
> Sounds like a good start.
>
> So the only reason we’re running tests sequentially is because of memory
> usage concerns?
>
> Thanks,
> Ludo’.
[-- Attachment #2: Type: text/html, Size: 3903 bytes --]
next prev parent reply other threads:[~2019-04-04 17:38 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
2019-04-04 15:47 ` Ivan Petkov
2019-04-04 16:06 ` Ludovic Courtès
2019-04-04 17:37 ` Ivan Petkov [this message]
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=17B412D1-5D9A-40C8-B37E-D8C08F0E9641@gmail.com \
--to=ivanppetkov@gmail.com \
--cc=35139@debbugs.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 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).