GNU bug report logs - #26441
Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores

Previous Next

Full log

View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Bruno Haible <bruno <at> clisp.org>
Cc: Mathieu Othacehe <m.othacehe <at> gmail.com>, bug-gnulib <at> gnu.org, 26441 <at> debbugs.gnu.org
Subject: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores
Date: Wed, 12 Apr 2017 18:11:22 +0200

Hi Bruno,

Bruno Haible <bruno <at> clisp.org> skribis:

>> The ‘test-lock’ test as shipped with gettext-0.19.8.1 fails to complete
>> (or hangs?) on machines with 32+ cores, as reported here:
>> 
>>   https://bugs.gnu.org/26441
>> 
>> Does that ring a bell?
>
> Yes, this is the bug that was investigated in December 2016 [1] and
> subsequently fixed [2].
>
>> Mathieu Othacehe found that this is fixed by gettext commit
>> 1afbcb06fded2a427b761dd1615b1e48e1e853cc but writes:
>> 
>> > However, I don't fully understand the difference between commit
>> > 1afbcb06fded2a427b761dd1615b1e48e1e853cc in gettext and commit
>> > 480d374e596a0ee3fed168ab42cd84c313ad3c89 in gnulib.
>
> gettext contains two copies of test-lock.c, one from gnulib and
> a another one that doesn't use gnulib.
> The commit 480d374e596a0ee3fed168ab42cd84c313ad3c89 in gnulib fixed
> the first one.
> The commit 1afbcb06fded2a427b761dd1615b1e48e1e853cc in gettext fixed
> the second one, in the same way.

OK, thanks for the explanation.  I guess we’ll borrow the relevant
patches.

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.