-
-
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
test_open_mfdataset_list_attr is ran even when dask is not available #3777
Comments
Thanks for finding these @ArchangeGabriel That one looks like a reasonably easy fix; we just need to surround that test with the standard requires dask decorator... |
The test is here: xarray/xarray/tests/test_backends.py Line 2543 in 52ee5df
there is probably no test environment that has netCDF4 but not dask |
You mean in your test matrix? Then yes. Anyway, I’ve proposed a simple fix in #3780, not sure if you want to go a different route (like making the test work without dask, not sure if that makes any sense). |
Yes, I was wondering why this was not caught anywhere & I think #3780 is fine. |
Well, you can’t test every combination of dependencies, especially with the large number of optional ones you have. ;) |
I’m currently packaging xarray (0.15.0) for ArchLinux, and I’m running the test suite with all our currently available packages (in addition to
python-numpy
,python-pandas
andpython-pytest
of course):I was greatly impressed at the automatic selection of tests depending on what is available on the system. :) I’m only seeing 10 tests failures (
10 failed, 8057 passed, 1384 skipped, 518 xfailed, 277 xpassed, 5268 warnings
), and amongst them one is happening because a test requiring dask is run even without it being installed:test_open_mfdataset_list_attr
.Corresponding test output:
I think this test should thus not be selected if dask is not installed. ;)
The text was updated successfully, but these errors were encountered: