-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix compatibility with h5py version 3 and unpin tests #4570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@mathause A quick check running |
The longer I look at that trying to find the differences the more confused I get. Any hints appreciated. Trying to catch up tomorrow. |
I opened an issue over at h5netcdf (h5netcdf/h5netcdf#81) with my current evaluations. |
This should possibly be resolved by h5netcdf/h5netcdf#82. At least the xarray testsuite runs with that |
I've updated h5netcdf/h5netcdf#82. Review from xarray-folks very much appreciated. |
There is a potential fix in #4893. |
h5py version 3.1 broke our tests. I pinned it to version 2.10 in #4569. We should therefore
The failures could be related to a change how strings are read: https://docs.h5py.org/en/latest/strings.html I am not sure if this has to be fixed in xarray or in h5necdf. I'd be happy if someone else took this one.
Failed tests:
Example failure:
The text was updated successfully, but these errors were encountered: