Closed caspervdw closed 3 years ago
So far, these tests run fine on my local machine with pytables 3.6.1. I'll investigate further.
Looks like this is only when using pytables 3.6 with an older hdf5. The GitHub Workflows builds are using hdf5 1.10.4 and this test passes.
Also, from looking at the test code it's unclear how the same file could ever be opened multiple times. So this is likely just an outright bug when using these versions of pytables and hdf5 together.
Oh! Now I see that the pip environment has the older version of hdf5. My work continues…
I think I've found the problem. It appears that the Linux pytables wheel for python 3.9 includes the pre-built binary for hdf5 version 1.8.5patch1 (released in 2010). When it is imported, pytables does not use the newer hdf5 that your script had already installed via apt.
The equivalent wheels for python 3.8 and 3.7 do not include binaries. So perhaps this is a mistake?
Thanks for diving into this @nkeim ! I think we can view this as a PyTables packaging issue and safely ignore (skip) the test on this specific environment.
In view of the large build time, I would like to stick to the binary wheels.
See builds e.g. https://github.com/caspervdw/trackpy/runs/1946300547
The important part of the traceback:
The question is: can we repare this, or do we need to constrain to PyTables < 3.6?
@nkeim Do you have any thoughts about this?
Full traceback: