CI: Nightly optional-deps #57
ci-nightly.yml
on: schedule
find-wheels
6s
Nightly numba-cuda (linux-aarch64)
/
compute-matrix
5s
Nightly PyTorch (linux-aarch64)
/
compute-matrix
5s
Nightly standard (linux-aarch64)
/
compute-matrix
4s
Matrix: Nightly numba-cuda (linux-64) / test
Matrix: Nightly numba-cuda (linux-aarch64) / test
Matrix: Nightly numba-cuda (win-64) / test
Matrix: Nightly PyTorch (linux-aarch64) / test
Matrix: Nightly PyTorch (linux-64) / test
Matrix: Nightly PyTorch (win-64) / test
Matrix: Nightly standard (linux-aarch64) / test
Nightly check status
3s
Annotations
14 errors
|
Nightly PyTorch (linux-aarch64) / Python 3.12, CUDA 13.0.2 (wheels), GPU l4, 2.11.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-64) / Python 3.12, CUDA 13.0.2 (wheels), GPU l4, 2.11.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-aarch64) / Python 3.12, CUDA 12.6.3 (wheels), GPU l4, 2.9.1
Process completed with exit code 2.
|
|
Nightly PyTorch (linux-aarch64) / Python 3.12, CUDA 12.6.3 (wheels), GPU l4, 2.9.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-aarch64) / Python 3.12, CUDA 13.0.2 (wheels), GPU l4, 2.9.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-64) / Python 3.12, CUDA 13.0.2 (wheels), GPU l4, 2.9.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-64) / Python 3.12, CUDA 12.6.3 (wheels), GPU l4, 2.9.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-64) / Python 3.12, CUDA 12.6.3 (wheels), GPU l4, 2.11.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly PyTorch (linux-aarch64) / Python 3.12, CUDA 12.6.3 (wheels), GPU l4, 2.11.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly numba-cuda (linux-aarch64) / Python 3.12, CUDA 13.3.0 (wheels), GPU l4, latest
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly numba-cuda (linux-aarch64) / Python 3.12, CUDA 12.9.1 (wheels), GPU l4, latest
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly numba-cuda (linux-64) / Python 3.12, CUDA 12.9.1 (wheels), GPU l4, latest
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly numba-cuda (linux-64) / Python 3.12, CUDA 13.3.0 (wheels), GPU l4, latest
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
Nightly check status
Process completed with exit code 1.
|