Subject: Re: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores

From: [email-masked] (Ludovic Courtès)
Date: Wed, 12 Apr 2017 13:53:57 +0200

[email-masked] (Ludovic Courtès) 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 information
>   +   between threads.  If set to 0, a lock is used to protect these variables.
>   +   If set to 1, 'volatile' is used; this is theoretically equivalent but 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=18000 didn’t help…

Ludo’.