Skip to content
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

⚠️ Nightly upstream-dev CI failed ⚠️ #4807

Closed
github-actions bot opened this issue Jan 14, 2021 · 6 comments
Closed

⚠️ Nightly upstream-dev CI failed ⚠️ #4807

github-actions bot opened this issue Jan 14, 2021 · 6 comments
Labels
CI Continuous Integration tools

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jan 14, 2021

Workflow Run URL

Python 3.8 Test Summary Info
FAILED xarray/tests/test_backends.py::TestNetCDF4Data::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestNetCDF4ViaDaskData::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestZarrDictStore::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestZarrDirectoryStore::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestScipyInMemoryData::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestScipyFileObject::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestScipyFilePath::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestNetCDF3ViaNetCDF4Data::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestNetCDF4ClassicViaNetCDF4Data::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestGenericNetCDFData::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestH5NetCDFData::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestH5NetCDFFileObject::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_backends.py::TestH5NetCDFViaDaskData::test_roundtrip_string_with_fill_value_nchar
FAILED xarray/tests/test_conventions.py::TestCFEncodedDataStore::test_roundtrip_string_with_fill_value_nchar
@github-actions github-actions bot added the CI Continuous Integration tools label Jan 14, 2021
@mathause
Copy link
Collaborator

  • I wonder if that has something to do with coords: retain str dtype #4759. But why would this only fail upstream?
  • It is also similar to fix compatibility with h5py version 3 and unpin tests #4570 but h5py is still pinned...
  • Some of also seems to be correctly failing: we have encoding = {"dtype": "S1"} but expected has dtype U1.
  • The tests are enclosed with with pytest.raises(NotImplementedError): should these not fail if no error is raised? So why do we even get a result...
  • Why are some dask arrays not evaluated in assert_identical?

@keewis
Copy link
Collaborator

keewis commented Jan 14, 2021

this is unrelated to #4759, the errors appeared before that (see https://github.com/pydata/xarray/runs/1684617075). The issue was opened today because the scheduled CI was broken until the merge of #4806.

@mathause
Copy link
Collaborator

I guess the failure could easily be fixed - replace "abc" by b"abc" but the question is - why does this raise a NotImplementedError and still manage to write the file (for all backends)? When I try it locally I only get an empty netCDF.

@keewis
Copy link
Collaborator

keewis commented Jan 19, 2021

interestingly, this didn't fail in the run yesterday. As far as I can tell, only the versions of identify, bottleneck, numpy, and pandas changed. Not sure if any of these could have fixed this. Maybe we did without noticing it?

@mathause
Copy link
Collaborator

As it touches all backends my bet would be on numpy or pandas - maybe numpy/numpy#18152? I think it's not really worth digging - so I suggest to close this.

@keewis
Copy link
Collaborator

keewis commented Jan 19, 2021

that makes sense, I agree we don't really have to figure out what the actual cause was. If this pops up again we can just wait on the CI to open a new issue.

@keewis keewis closed this as completed Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration tools
Projects
None yet
Development

No branches or pull requests

2 participants