[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >
|
From: |
Bruno Haible |
|
Subject: |
Re: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores |
|
Date: |
Wed, 12 Apr 2017 16:37:03 +0200 |
|
User-agent: |
KMail/5.1.3 (Linux/4.4.0-71-generic; KDE/5.18.0; x86_64; ; ) |
Hi Ludo,
> 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.
Bruno
[1] https://lists.gnu.org/archive/html/bug-gnulib/2016-12/msg00113.html
[2]
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=480d374e596a0ee3fed168ab42cd84c313ad3c89