pydata / pydata/xarray

⚠️ Nightly upstream-dev CI failed ⚠️

Open
#11,501 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CI
Dominant language
Python
Stars
4.2k
Forks
1.4k
Avg merge
2d 15h
Merged PRs (30d)
14

Description

Workflow Run URL

Python 3.13 Test Summary
xarray/tests/test_dataarray.py::TestIrisConversion::test_to_and_from_iris: TypeError: Strings must be encoded before hashing
xarray/tests/test_dataarray.py::TestIrisConversion::test_to_and_from_iris_dask: TypeError: Strings must be encoded before hashing
xarray/tests/test_duck_array_ops.py::test_reduce[None-False-min-False-bool-1]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(True)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[None-False-min-False-bool-2]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(False)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[None-False-max-False-bool-1]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(True)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[None-False-max-False-bool-2]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(True)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[x-False-min-False-bool-1]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(True)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[x-False-min-False-bool-2]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array([nan, nan, nan, False, False, False, True, False], dtype=object)
R
    array([nan, nan, nan, nan, nan, nan, nan, nan])
xarray/tests/test_duck_array_ops.py::test_reduce[x-False-max-False-bool-1]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array(True)
R
    array(nan)
xarray/tests/test_duck_array_ops.py::test_reduce[x-False-max-False-bool-2]: AssertionError: Left and right DataArray objects are not close
Differing values:
L
    array([nan, nan, nan, False, True, True, True, True], dtype=object)
R
    array([nan, nan, nan, nan, nan, nan, nan, nan])
xarray/tests/test_variable.py::TestAsCompatibleData::test_tz_datetime: pandas.errors.Pandas4Warning: Series.values returning an ndarray that drops timezone information for DatetimeTZDtype is deprecated. In a future version, this will return the underlying DatetimeArray instead. Use 'Series.to_numpy()' to get a NumPy array, or 'Series.array' to get the ExtensionArray.
xarray/tests/test_variable.py::test_datetime_conversion[0   2000-01-01 00:00:00-05:00\ndtype: datetime64[ns, America/New_York]-ns]: pandas.errors.Pandas4Warning: Series.values returning an ndarray that drops timezone information for DatetimeTZDtype is deprecated. In a future version, this will return the underlying DatetimeArray instead. Use 'Series.to_numpy()' to get a NumPy array, or 'Series.array' to get the ExtensionArray.
xarray/tests/test_variable.py::test_pandas_two_only_datetime_conversion_warnings[series-timezone]: pandas.errors.Pandas4Warning: Series.values returning an ndarray that drops timezone information for DatetimeTZDtype is deprecated. In a future version, this will return the underlying DatetimeArray instead. Use 'Series.to_numpy()' to get a NumPy array, or 'Series.array' to get the ExtensionArray.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked workflow run and reproduce the Python 3.13 failures in xarray/tests/test_dataarray.py, xarray/tests/test_duck_array_ops.py, and xarray/tests/test_variable.py. Trace the reported hashing, boolean-reduction, and timezone warnings to their causes; done means the listed tests pass cleanly in the upstream-dev CI run.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, pandas, python
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.