Bug#1010202: MatIO test failures against HDF5 1.12.0

[Gilles Filippini]

Hi,

Thomas Beutlich a écrit le 19/05/2022 à 22:36 :
> Hi Sébastien,
> 
> seems I was right (and somehow remembered correctly) with my guess of 
> some concurrency issue when running the testsuite. For my own test setup 
> I chose to go with serial execution of the testsuite (if matio is built 
> with libhdf5 support).
> 
> Best regards,
> Thomas
> 
> Am 19.05.2022 um 10:06 schrieb Sébastien Villemot:
>> Hi Thomas,
>>
>> It turns out that running the testsuite sequentially fixes the problem,
>> as explained by Gilles Filippini (who maintains HDF5 in Debian), see:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010202#25
>>
>> Where do we go from here? We now have a workaround, but that’s hardly
>> satisfactory.
>>
>> If possible, please reply by
>> putting pini at debian.org and 1010202 at bugs.debian.org in CC, so that this
>> it is properly tracked in our system.
>>
>> Best regards,
>>
>> Le mardi 03 mai 2022 à 20:59 +0200, Thomas Beutlich a écrit :
>>> Hi Sébastien,
>>> it is the same test case that fails for three different HDF5-based
>>> MAT files. My guess is some concurrency issue of the hdf5lib. Can you
>>> please try:
>>> * to run the testsuite sequentially
>>>   * to not build libhdf with --enable-parallel, i.e. to have the
>>> serial version of hdf5lib
>>>   * set env var HDF5_USE_FILE_LOCKING=FALSE

Setting the above environment variable fixes the problem when running 
the testsuite in parallel mode.

Best,

_g.