From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26441: =?UTF-8?Q?Gnulib=E2=80=99s_?= =?UTF-8?Q?=E2=80=98test-lock=E2=80=99?= fails to complete on machines with >= 32 cores Date: Wed, 12 Apr 2017 13:53:57 +0200 Message-ID: <878tn5et9m.fsf@gnu.org> References: <871sszuznt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cyGra-0007H0-SS for bug-guix@gnu.org; Wed, 12 Apr 2017 07:55:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cyGrW-0004dJ-1q for bug-guix@gnu.org; Wed, 12 Apr 2017 07:55:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:45687) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cyGrV-0004dD-UO for bug-guix@gnu.org; Wed, 12 Apr 2017 07:55:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cyGrV-0005ME-L4 for bug-guix@gnu.org; Wed, 12 Apr 2017 07:55:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871sszuznt.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 11 Apr 2017 10:16:54 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 26441@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) skribis: > This may be fixed by Gnulib commit > 480d374e596a0ee3fed168ab42cd84c313ad3c89 (not present in > gettext-0.19.8.1), which introduces this: > > --- a/tests/test-lock.c > +++ b/tests/test-lock.c > @@ -50,6 +50,13 @@ > Uncomment this to see if the operating system has a fair scheduler.= */ > #define EXPLICIT_YIELD 1 > > +/* Whether to use 'volatile' on some variables that communicate inform= ation > + between threads. If set to 0, a lock is used to protect these vari= ables. > + If set to 1, 'volatile' is used; this is theoretically equivalent b= ut can > + lead to much slower execution (e.g. 30x slower total run time on a = 40-core > + machine. */ > +#define USE_VOLATILE 0 > > 30x slower could exceed the default max-silent-timeout, which is 1 hour. Maybe not: building with --max-silent-time=3D18000 didn=E2=80=99t help=E2= =80=A6 Ludo=E2=80=99.