unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ivan Petkov <ivanppetkov@gmail.com>
Cc: 35126@debbugs.gnu.org
Subject: [bug#35126] [PATCH] gnu: rust: Enable parallel tests starting with 1.26.
Date: Thu, 4 Apr 2019 20:29:38 +0200	[thread overview]
Message-ID: <20190404202929.7b932d3b@scratchpost.org> (raw)
In-Reply-To: <D0EF2544-CBB0-4ED2-BCF1-DCACAE7A8704@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

Hi Ivan,

On Wed, 3 Apr 2019 17:52:35 -0700
Ivan Petkov <ivanppetkov@gmail.com> wrote:

> Functionally, it looks good to me (and should speed up all subsequent builds)!
> 
> Just curious, any reason why we’re doing this starting 1.26 and not earlier?

There have been problems with it in very old Rust builds which is why it was
disabled in the first place.

Icecat uses Rust 1.24 - I selfishly don't want to change that one because I
use it ;)

And I'm not sure when (in which version) they fixed the parallel tests (if
they fixed them, that is).

So I'm kinda starting in the middle...

(I'm now up to and excluding rust 1.30.1 with enabled parallel tests with -j4)
(rust 1.30.1 is still building for a few rounds)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-04-04 18:30 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 [this message]
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
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=20190404202929.7b932d3b@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=35126@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).