issues

What happened?

I'm the Debian maintainer of xarray. I'm packaging 2024.01.1, and. running tests we see 4 failures on python3.11.

What did you expect to happen?

No failures in unit tests

Minimal Complete Verifiable Example

No response

MVCE confirmation

• [X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
• [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
• [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
• [X] New issue — a search of GitHub Issues suggests this is not a duplicate.
• [X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output

```Python On python3.11, python3.12 we see:

FAILED xarray/tests/test_units.py::TestVariable::test_isel[int64-single value-single indexer-True] - TypeError: ones_like() got an unexpected keyword argument 'subok' FAILED xarray/tests/test_units.py::TestVariable::test_isel[int64-multiple values-single indexer-True] - TypeError: ones_like() got an unexpected keyword argument 'subok' FAILED xarray/tests/test_units.py::TestVariable::test_isel[int64-single value-multiple indexers-True] - TypeError: ones_like() got an unexpected keyword argument 'subok' FAILED xarray/tests/test_units.py::TestVariable::test_isel[int64-multiple values-multiple indexers-True] - TypeError: ones_like() got an unexpected keyword argument 'subok' This in detail looks like:

  return da_func(*args, **kwargs)

E TypeError: ones_like() got an unexpected keyword argument 'subok'

/usr/lib/python3/dist-packages/dask/array/core.py:1760: TypeError so in. test_units.py its passing `subok` from xarray into `numpy.ones_like` for some reason.

Anything else we need to know?

The code is at :

https://salsa.debian.org/science-team/python-xarray/-/tree/debian/latest?ref_type=heads

Environment

Additional packages/plugins used:

What is your issue?

I'm Debian maintainer for xarray.

https://tracker.debian.org/pkg/python-xarray

Debian/Ubuntu builds packages offline, from a frozen tarball (or possibly a small <5 number tarballs). xarray requires external objects for both building documentation and testing (we can do testing on our own CI/CD pipelines). Recent releases use pooch to download/cache test objects. We need a method of stating where the cache is (/home not an option -- that is directed to /non-existant on our build systems).

Can this be implemented, or how do you suggest we proceed?

Best regards Alastair McKinstry

What happened?

This is on Debian, which supports the S390/s390X archs from IBM.

For the 2022.06.0 release: ======================================================================================== short test summary info ======================================================================================== FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[365_day] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[360_day] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[julian] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[all_leap] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[366_day] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[gregorian] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-14 16:00:00 FAILED xarray/tests/test_accessor_dt.py::test_calendar_cftime_2D[proleptic_gregorian] - pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: -809793270280017-04-1

Details are tracked here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004870

What did you expect to happen?

No response

Minimal Complete Verifiable Example

No response

MVCE confirmation

• [ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
• [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
• [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
• [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output

No response

Anything else we need to know?

No response

Environment

Test failure with dask

Packaging xarray 0.10.4 fails on Debian (where 0.10.3 succeeds).

```python ___ TestDataArrayAndDataset.test_dot ___

args = ('...ab,...b->...a', dask.array<array, shape=(4, 6), dtype=float64, chunksize=(2, 2)>, dask.array<getitem, shape=(6,), dtype=float64, chunksize=(2,)>) kwargs = {} dispatch_args = (dask.array<array, shape=(4, 6), dtype=float64, chunksize=(2, 2)>, dask.array<getitem, shape=(6,), dtype=float64, chunksize=(2,)>)

def f(*args, **kwargs):
    if list_of_args:
        dispatch_args = args[0]
    else:
        dispatch_args = args[array_args]
    if any(isinstance(a, dask_array.Array) for a in dispatch_args):
        try:

          wrapped = getattr(dask_module, name)

E AttributeError: module 'dask.array' has no attribute 'einsum'

xarray/core/duck_array_ops.py:48: AttributeError

```

Problem description

Versions used: python 3.6 xarray 0.10.4 dask 0.16.0

Full build log attached. python-xarray_0.10.4-1_amd64.build.txt