-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Potential test failures with libnetcdf 4.5.0 #1721
Comments
@spencerahill how did you install libnetcdf 4.5.0? I'm still getting 4.4.1 with conda, on both the default and conda-forge channel. |
@shoyer I initially ran into that too. I think depending on the libraries you have installed (or seek to install) conda may not let you upgrade to libnetcdf 4.5.0. To get libnetcdf 4.5.0 I created a clean environment with the following specification file:
Then from within that environment I did an editable install of the xarray master branch and ran the test suite. |
@spencerkclark conda-forge has |
@ocefpaf thanks, empirically the original did the trick, but I have edited it for correctness. |
I ran our test suite with libnetcdf 4.5.0 and it turned up two failures, for I'll have to do a little digging to turn up exactly which cross read/write cases failed. (It would probably be best to edit the test cases to use parameterized tests of some sort rather than the explicit "for" loop) |
Thanks @shoyer, I think it's the files written by the 'scipy' engine and read by the 'netcdf4' engine. Here is a minimal example:
Here's a link to the issue upstream: Unidata/netcdf-c#657. |
In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
A heads up: @spencerkclark unearthed problems with libnetcdf 4.5.0 that will cause xarray test failures. See Unidata/netcdf4-python#742 and link therein for more info.
The text was updated successfully, but these errors were encountered: