id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type 2112335677,I_kwDOAMm_X8595689,8692,test failure on 2024.01.1,915118,closed,0,,,2,2024-02-01T11:57:41Z,2024-02-02T08:15:18Z,2024-02-02T08:15:18Z,NONE,,,,"### 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](https://mybinder.org/v2/gh/pydata/xarray/main?urlpath=lab/tree/doc/examples/blank_template.ipynb), 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:
Get: 1 http://deb.debian.org/debian sid/main arm64 libc-ares2 arm64 1.26.0-1 [140 kB] Get: 2 http://deb.debian.org/debian sid/main arm64 python-hypothesis-doc all 6.93.2-1 [511 kB] Get: 3 http://deb.debian.org/debian sid/main arm64 python-scipy-doc all 1.10.1-10 [33.4 MB] Get: 4 http://deb.debian.org/debian sid/main arm64 python3-asciitree all 0.3.3-4 [5612 B] Get: 5 http://deb.debian.org/debian sid/main arm64 python3-more-itertools all 10.2.0-1 [59.9 kB] Get: 6 http://deb.debian.org/debian sid/main arm64 python3-scipy arm64 1.10.1-10 [17.8 MB] Get: 7 http://deb.debian.org/debian sid/main arm64 python3-markupsafe arm64 2.1.4-1 [14.6 kB] Get: 8 http://deb.debian.org/debian sid/main arm64 python3-xarray all 2023.12.0-3 [691 kB] Get: 9 http://deb.debian.org/debian sid/main arm64 python3-monotonic all 1.6-2 [5728 B] Get: 10 http://deb.debian.org/debian sid/main arm64 python3-fasteners all 0.18-2 [14.0 kB] Get: 11 http://deb.debian.org/debian sid/main arm64 python3-sortedcontainers all 2.4.0-2 [31.9 kB] Get: 12 http://deb.debian.org/debian sid/main arm64 python3-hypothesis all 6.93.2-1 [294 kB] Get: 13 http://deb.debian.org/debian sid/main arm64 python3-numcodecs arm64 0.12.1+ds-1+b1 [424 kB] Get: 14 http://deb.debian.org/debian sid/main arm64 python3-pydata-sphinx-theme all 0.7.2-3 [1075 kB] Get: 15 http://deb.debian.org/debian sid/main arm64 python3-sphinx-copybutton all 0.4.0-4 [16.0 kB] Get: 16 http://deb.debian.org/debian sid/main arm64 python3-sphinx-gallery all 0.10.1-4 [122 kB] Get: 17 http://deb.debian.org/debian sid/main arm64 python3-sphinx-inline-tabs all 2023.4.21-1 [35.9 kB] Get: 18 http://deb.debian.org/debian sid/main arm64 python3-zarr all 2.16.1+ds-2 [1311 kB]
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8692/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue 1869941964,I_kwDOAMm_X85vdQzM,8119,No-download mode needed for build,915118,open,0,,,2,2023-08-28T15:03:03Z,2023-09-15T14:39:36Z,,NONE,,,,"### 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 ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8119/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue 1334835539,I_kwDOAMm_X85Pj_lT,6906,regression in cftime on s390 ,915118,open,0,,,10,2022-08-10T15:53:54Z,2022-09-17T12:20:41Z,,NONE,,,,"### 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](https://mybinder.org/v2/gh/pydata/xarray/main?urlpath=lab/tree/doc/examples/blank_template.ipynb), 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
Debian Sid cftime 1.6.1 pandas 1.3.5+dfsg python 3.10 This is in a build environment to test any possible fixes or debug.
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6906/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue 325172935,MDU6SXNzdWUzMjUxNzI5MzU=,2167,0.10.4 fails test suite on Debian: dask.array has no attribute 'einsum',915118,closed,0,,,4,2018-05-22T07:33:59Z,2018-05-23T14:27:30Z,2018-05-23T14:27:30Z,NONE,,,,"#### 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, dask.array) kwargs = {} dispatch_args = (dask.array, dask.array) 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](https://github.com/pydata/xarray/files/2025446/python-xarray_0.10.4-1_amd64.build.txt) ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/2167/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue