From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#35139: Rust builds systematically time out
Date: Thu, 04 Apr 2019 18:06:07 +0200
Message-ID: <87imvtrc0g.fsf@gnu.org>
References: <878swqtabb.fsf@gnu.org> <87bm1mglus.fsf@gmx.com>
	<101FBDE5-97FA-4449-9076-DD24C56B8715@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:39377)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hC4tL-0005tb-N7
	for bug-guix@gnu.org; Thu, 04 Apr 2019 12:07:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hC4tK-0002lq-OF
	for bug-guix@gnu.org; Thu, 04 Apr 2019 12:07:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:59293)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1hC4tK-0002kj-GL
	for bug-guix@gnu.org; Thu, 04 Apr 2019 12:07:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hC4tJ-0003gH-Vm
	for bug-guix@gnu.org; Thu, 04 Apr 2019 12:07:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.35139.B.155439399514099@debbugs.gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:39194)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1hC4sl-0005IN-6R
	for bug-guix@gnu.org; Thu, 04 Apr 2019 12:06:28 -0400
In-Reply-To: <101FBDE5-97FA-4449-9076-DD24C56B8715@gmail.com> (Ivan Petkov's
	message of "Thu, 4 Apr 2019 08:47:42 -0700")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ivan Petkov <ivanppetkov@gmail.com>
Cc: 35139@debbugs.gnu.org

Ivan Petkov <ivanppetkov@gmail.com> skribis:

>> On Apr 4, 2019, at 1:59 AM, Ludovic Court=C3=A8s <ludo@gnu.org> wrote:
>>=20
>> 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 =E2=80=9Cembarrassingly parallel=
=E2=80=9D, but
>> we=E2=80=99re running tests with =E2=80=98-j1=E2=80=99.)
>>=20
>> To summarize, there are two problems:
>>=20
>>  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=E2=80=99t 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=E2=80=99re running tests sequentially is because of m=
emory
usage concerns?

Thanks,
Ludo=E2=80=99.