[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Ludovic Courtès
Subject: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores
Date: Wed, 12 Apr 2017 18:11:22 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Hi Bruno,

Bruno Haible <address@hidden> skribis:

>> The ‘test-lock’ test as shipped with gettext- 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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]