-
Notifications
You must be signed in to change notification settings - Fork 42
fix tests #81
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
fix tests #81
Conversation
Ah this makes sense. Can you move |
It will not pass unless we use the most current version of Xarray on Github (with the recent PR). I can add this to whats-new.rst -- should I do so under v0.2.1 or create the v0.2.2 header? |
The coarsen tests are skipped so that should not be needed? LEt'add a whats-new note under 0.2.2 |
Hmm that's interesting. If I run "pip install git+git://github.com/pydata/xarray.git", |
@dcherian I ran
So one |
ah nice debugging skills! Let's skip that second coarsen test too then. |
Co-authored-by: Deepak Cherian <[email protected]>
Great. Thanks @jukent |
I found a bug in
test_getitem_errors
which needed a deep copy before deleting the attributes. Other issues have to do withxr.coarsen
(particularly intest_kwargs_expand_key_to_multiple_keys
) that was fixed by this PR (pydata/xarray#4360). Once the newest version of Xarray is released these tests will not have to be run in a specific order to pass.Closes #47