You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest scheduled CI for "Test Upstream Dependencies" passed. Which is suspicious as #1920 fails. When I looked at the pip list, I saw that xarray 2024.07.0 was being used. The pip install earlier in the build failed:
Collecting xarray@ git+https://github.com/pydata/xarray.git@main (from -r CI/requirements_upstream.txt (line 6))
Cloning https://github.com/pydata/xarray.git (to revision main) to /tmp/pip-install-1dx63znp/xarray_790fcd7be3824fdbab99794a83e780d9
Running command git clone --filter=blob:none --quiet https://github.com/pydata/xarray.git /tmp/pip-install-1dx63znp/xarray_790fcd7be3824fdbab99794a83e780d9
Resolved https://github.com/pydata/xarray.git to commit 8db6bc9048dc639f8d33c4d4c921da0df3d14cd2
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Requirement already satisfied: pandas>=1.5 in /home/runner/micromamba/envs/xclim/lib/python3.10/site-packages (from flox@ git+https://github.com/xarray-contrib/flox.git@main->-r CI/requirements_upstream.txt (line 3)) (2.2.2)
Requirement already satisfied: packaging>=21.3 in /home/runner/micromamba/envs/xclim/lib/python3.10/site-packages (from flox@ git+https://github.com/xarray-contrib/flox.git@main->-r CI/requirements_upstream.txt (line 3)) (24.1)
Requirement already satisfied: numpy-groupies>=0.9.19 in /home/runner/micromamba/envs/xclim/lib/python3.10/site-packages (from flox@ git+https://github.com/xarray-contrib/flox.git@main->-r CI/requirements_upstream.txt (line 3)) (0.11.2)
Requirement already satisfied: toolz in /home/runner/micromamba/envs/xclim/lib/python3.10/site-packages (from flox@ git+https://github.com/xarray-contrib/flox.git@main->-r CI/requirements_upstream.txt (line 3)) (0.12.1)
Requirement already satisfied: scipy>=1.9 in /home/runner/micromamba/envs/xclim/lib/python3.10/site-packages (from flox@ git+https://github.com/xarray-contrib/flox.git@main->-r CI/requirements_upstream.txt (line 3)) (1.14.1)
INFO: pip is looking at multiple versions of numba to determine which version is compatible with other requirements. This could take a while.
ERROR: Ignored the following versions that require a different python version: 0.36.0 Requires-Python >=3.6,<3.10; 0.37.0 Requires-Python >=3.7,<3.10
ERROR: Could not find a version that satisfies the requirement llvmlite<0.45,>=0.44.0dev0 (from numba) (from versions: 0.2.0, 0.2.1, 0.2.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0.1, 0.12.1, 0.13.0, 0.14.0, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.18.0, 0.19.0, 0.20.0, 0.21.0, 0.22.0, 0.23.0, 0.23.2, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 0.27.1, 0.28.0, 0.29.0, 0.30.0, 0.31.0, 0.32.0, 0.32.1, 0.33.0, 0.34.0, 0.35.0, 0.38.0, 0.38.1, 0.39.0, 0.39.1, 0.40.0rc1, 0.40.0, 0.40.1rc1, 0.40.1, 0.41.0rc1, 0.41.0, 0.41.1, 0.42.0rc1, 0.42.0, 0.43.0rc1, 0.43.0)
ERROR: No matching distribution found for llvmlite<0.45,>=0.44.0dev0
Not sure I fully understand the issue, but at least I see that pip raised an "ERROR" without the build failing! This might explain why we were unaware of all these xarray 2024.9 bugs!
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Generic Issue
The latest scheduled CI for "Test Upstream Dependencies" passed. Which is suspicious as #1920 fails. When I looked at the pip list, I saw that xarray 2024.07.0 was being used. The pip install earlier in the build failed:
Not sure I fully understand the issue, but at least I see that pip raised an "ERROR" without the build failing! This might explain why we were unaware of all these xarray 2024.9 bugs!
Code of Conduct
The text was updated successfully, but these errors were encountered: