From: Ivan Petkov <ivanppetkov@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35126@debbugs.gnu.org
Subject: [bug#35126] [PATCH] gnu: rust: Enable parallel tests starting with 1.26.
Date: Sat, 6 Apr 2019 09:09:13 -0700 [thread overview]
Message-ID: <90EB17C1-533B-4E1A-8709-990CF41D6E82@gmail.com> (raw)
In-Reply-To: <20190406124815.0d448082@scratchpost.org>
> On Apr 6, 2019, at 3:48 AM, Danny Milosavljevic <dannym@scratchpost.org> wrote:
>
> On Fri, 5 Apr 2019 08:36:44 -0700
> Ivan Petkov <ivanppetkov@gmail.com> wrote:
>
>> Hi Danny,
>>
>>> On Apr 5, 2019, at 7:11 AM, Danny Milosavljevic <dannym@scratchpost.org> wrote:
>>>
>>> Should we limit the number of parallel jobs? I think at least armhf is going
>>> to be very overloaded otherwise. To which value?
>>
>> Do the armhf builders define that they have fewer cores available?
>>
>> If not, we could cap the max jobs to 2, although it would be nice to potentially
>> use as many cores as are available for non-armhf builds.
>
> I think the problem is RAM usage. Arm machines have little RAM and will choke
> if too many memory-expensive things run in parallel.
I’d anticipate that building rustc itself would be the most memory intense operation,
I think most of the individual tests aren’t anywhere nearly as big…
—Ivan
next prev parent reply other threads:[~2019-04-06 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 17:00 [bug#35126] [PATCH] gnu: rust: Enable parallel tests starting with 1.26 Danny Milosavljevic
2019-04-04 0:52 ` Ivan Petkov
2019-04-04 18:29 ` Danny Milosavljevic
2019-04-04 21:59 ` Ivan Petkov
2019-04-05 14:11 ` Danny Milosavljevic
2019-04-05 15:36 ` Ivan Petkov
2019-04-06 10:48 ` Danny Milosavljevic
2019-04-06 16:09 ` Ivan Petkov [this message]
2019-04-08 1:43 ` Ivan Petkov
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=90EB17C1-533B-4E1A-8709-990CF41D6E82@gmail.com \
--to=ivanppetkov@gmail.com \
--cc=35126@debbugs.gnu.org \
--cc=dannym@scratchpost.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).