[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: |
Ludovic Courtès |
Subject: |
Re: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores |
Date: |
Wed, 12 Apr 2017 14:00:50 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello Gnulib,
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?
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.
Could you clarify this?
Thanks in advance,
Ludo’.
- Re: bug#26441: Gnulib’s ‘test-lock’ fails to complete on machines with >= 32 cores,
Ludovic Courtès <=