Closed dcherian closed 2 years ago
Thanks @dcherian for the ping. Most likely due to upstream change (recent merge) in h5netcdf. Investigating this the next days.
OMG, that's already failing for 12 days. How could we miss this?
our github action updates any existing open "nightly test failed" issue and we forgot to close the last one...
I'll add two runs two h5netcdf CI, which check xarray h5netcdf related tests for latest release and latest commit to get an early warning if something breaks xarray.
What would be the correct pytest incantation to run all h5netcdf related tests?
Thanks! This seems to work (see https://docs.pytest.org/en/7.1.x/how-to/usage.html#specifying-which-tests-to-run).
> pytest -k "H5NetCDF"
==================================================================================================================================================== test session starts =====================================================================================================================================================
platform darwin -- Python 3.10.6, pytest-7.1.3, pluggy-1.0.0
rootdir: /Users/dcherian/work/python/xarray, configfile: setup.cfg, testpaths: xarray/tests, properties
plugins: xdist-2.5.0, forked-1.4.0, env-0.6.2, hypothesis-6.56.1, cov-4.0.0
collected 15998 items / 15723 deselected / 1 skipped / 275 selected
xarray/tests/test_backends.py .......................X.......x.......................................ss...................................X.......x.......................................ss...................................X.......x.......................................ss.............................. [ 99%]
xarray/tests/test_distributed.py .. [100%]
====================================================================================================================================================== warnings summary ======================================================================================================================================================
xarray/tests/test_backends.py::TestH5NetCDFData::test_zero_dimensional_variable
/Users/dcherian/mambaforge/envs/xarray-release/lib/python3.10/site-packages/cfgrib/xarray_plugin.py:11: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
if LooseVersion(xr.__version__) <= "0.17.0":
xarray/tests/test_backends.py::TestH5NetCDFData::test_zero_dimensional_variable
/Users/dcherian/mambaforge/envs/xarray-release/lib/python3.10/site-packages/setuptools/_distutils/version.py:346: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
other = LooseVersion(other)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=============================================================================================================== 263 passed, 7 skipped, 15723 deselected, 3 xfailed, 3 xpassed, 2 warnings in 86.98s (0:01:26) ================================================================================================================
/Users/dcherian/mambaforge/envs/xarray-release/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 4 leaked semaphore objects to clean up at shutdown
And I do something similar in flox with the groupby tests. It works really well!
Thanks a lot @dcherian, much appreciated.
@dcherian As assumed the source was a regression in __getitem__
-function over at h5netcdf. A patch is already merged. I've added a CI run against xarray github main to be on the safe side now and in future. Thanks for your help.
Thanks for the quick fix @kmuehlbauer !
What happened?
From upstream-dev CI: Workflow Run URL
Python 3.10 Test Summary
``` xarray/tests/test_backends.py::TestH5NetCDFData::test_orthogonal_indexing: AssertionError: Left and right Dataset objects are not identical Differing coordinates: L numbers (dim3) int64 0 1 2 0 0 R numbers (dim3) int64 ... L * dim3 (dim3)cc @benbovy @kmuehlbauer
Environment