Skip to content

Improve cuda_bindings examples #2898

Improve cuda_bindings examples

Improve cuda_bindings examples #2898

Triggered via push March 31, 2026 15:17
Status Cancelled
Total duration 22m 5s
Artifacts 75

ci.yml

on: push
Matrix: build-linux-64
Matrix: build-linux-aarch64
Matrix: build-windows
Matrix: test-linux-64
Matrix: test-linux-aarch64
Matrix: test-windows
Check job status
4s
Check job status
Fit to window
Zoom out
Zoom in

Annotations

127 errors, 49 warnings, and 18 notices
Test linux-aarch64 / py3.10, 13.0.2, wheels, a100
Process completed with exit code 1.
Test linux-aarch64 / py3.10, 13.0.2, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.10, 13.0.2, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.12, 13.2.0, wheels, a100
Process completed with exit code 1.
Test linux-aarch64 / py3.12, 13.2.0, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.12, 13.2.0, wheels, a100
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.
Test linux-aarch64 / py3.10, 13.2.0, wheels, a100
Process completed with exit code 1.
Test linux-aarch64 / py3.10, 13.2.0, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.10, 13.2.0, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.14t, 13.0.2, wheels, a100
Process completed with exit code 1.
Test linux-aarch64 / py3.14t, 13.0.2, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14t, 13.0.2, wheels, a100
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.
Test linux-64 / py3.10, 13.0.2, wheels, l4
Process completed with exit code 1.
Test linux-64 / py3.10, 13.0.2, wheels, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.10, 13.0.2, wheels, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-64 / py3.12, 13.0.2, wheels, l4
Process completed with exit code 1.
Test linux-64 / py3.12, 13.0.2, wheels, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.12, 13.0.2, wheels, l4
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.
Test linux-64 / py3.12, 13.2.0, wheels, l4
Process completed with exit code 1.
Test linux-64 / py3.12, 13.2.0, wheels, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.12, 13.2.0, wheels, l4
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.
Test linux-aarch64 / py3.11, 12.9.1, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.11, 12.9.1, wheels, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.12, 13.0.2, wheels, a100
Process completed with exit code 1.
Test linux-aarch64 / py3.12, 13.0.2, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.12, 13.0.2, wheels, a100
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.
Test linux-aarch64 / py3.14, 12.9.1, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14, 12.9.1, wheels, a100
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.
Test linux-aarch64 / py3.13, 12.9.1, wheels, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.13, 12.9.1, wheels, a100
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.
Test linux-64 / py3.11, 12.9.1, wheels, rtxpro6000
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.11, 12.9.1, wheels, rtxpro6000
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.14t, 12.9.1, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14t, 12.9.1, local, a100
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.
Test linux-aarch64 / py3.11, 13.0.2, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.11, 13.0.2, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-64 / py3.10, 13.2.0, wheels, l4
Process completed with exit code 1.
Test linux-64 / py3.10, 13.2.0, wheels, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.10, 13.2.0, wheels, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.14, 13.0.2, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14, 13.0.2, local, a100
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.
Test linux-64 / py3.11, 13.0.2, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.11, 13.0.2, local, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-64 / py3.10, 12.9.1, local, v100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.10, 12.9.1, local, v100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-64 / py3.13, 13.2.0, local, rtxpro6000
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 13.2.0, local, rtxpro6000
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.
Test linux-aarch64 / py3.13, 13.2.0, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.13, 13.2.0, local, a100
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.
Test linux-64 / py3.13, 13.0.2, local, rtxpro6000
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 13.0.2, local, rtxpro6000
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.
Test linux-aarch64 / py3.11, 13.2.0, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.11, 13.2.0, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.14t, 13.2.0, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14t, 13.2.0, local, a100
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.
Test linux-64 / py3.13, 13.0.2, local, h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 13.0.2, local, h100
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.
Test linux-64 / py3.13, 13.2.0, local, h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 13.2.0, local, h100
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.
Test linux-64 / py3.14t, 13.2.0, local, h100(x2)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14t, 13.2.0, local, h100(x2)
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.
Test linux-64 / py3.14, 12.9.1, wheels, t4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14, 12.9.1, wheels, t4
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.
Test linux-aarch64 / py3.12, 12.9.1, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.12, 12.9.1, local, a100
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.
Test linux-64 / py3.11, 13.2.0, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.11, 13.2.0, local, l4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-aarch64 / py3.13, 13.0.2, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.13, 13.0.2, local, a100
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.
Test linux-aarch64 / py3.10, 12.9.1, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.10, 12.9.1, local, a100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test linux-64 / py3.14, 13.0.2, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14, 13.0.2, local, l4
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.
Test linux-64 / py3.14t, 13.2.0, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14t, 13.2.0, local, l4
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.
Test linux-64 / py3.12, 12.9.1, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.12, 12.9.1, local, l4
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.
Test linux-64 / py3.14t, 12.9.1, local, t4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14t, 12.9.1, local, t4
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.
Test linux-64 / py3.14t, 13.0.2, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14t, 13.0.2, local, l4
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.
Test linux-64 / py3.14, 13.2.0, local, l4
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14, 13.2.0, local, l4
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.
Test linux-64 / py3.13, 12.9.1, wheels, v100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.13, 12.9.1, wheels, v100
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.
Test linux-64 / py3.14, 13.2.0, local, t4(x2)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-64 / py3.14, 13.2.0, local, t4(x2)
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.
Test win-64 / py3.14, 12.9.1, wheels, v100 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.14, 13.2.0, local, l4 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.14, 13.0.2, local, l4 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.14t, 12.9.1, local, l4 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.10, 12.9.1, wheels, rtx2080 (WDDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.10, 12.9.1, wheels, rtx2080 (WDDM)
The operation was canceled.
Test win-64 / py3.10, 13.0.2, local, rtxpro6000 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.10, 13.0.2, local, rtxpro6000 (TCC)
The operation was canceled.
Test win-64 / py3.13, 13.2.0, wheels, rtxpro6000 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.13, 13.2.0, wheels, rtxpro6000 (MCDM)
The operation was canceled.
Test win-64 / py3.12, 13.2.0, local, a100 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.12, 13.2.0, local, a100 (TCC)
The operation was canceled.
Test win-64 / py3.13, 13.0.2, wheels, rtxpro6000 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.13, 13.0.2, wheels, rtxpro6000 (MCDM)
The operation was canceled.
Test win-64 / py3.11, 13.2.0, wheels, rtx4090 (WDDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.11, 13.2.0, wheels, rtx4090 (WDDM)
The operation was canceled.
Test win-64 / py3.11, 12.9.1, local, v100 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.11, 12.9.1, local, v100 (MCDM)
The operation was canceled.
Test linux-aarch64 / py3.14, 13.2.0, local, a100
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test linux-aarch64 / py3.14, 13.2.0, local, a100
The operation was canceled.
Test linux-aarch64 / py3.14, 13.2.0, local, a100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Test linux-aarch64 / py3.14, 13.2.0, local, a100
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.
Test win-64 / py3.14t, 13.0.2, wheels, a100 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.14t, 13.0.2, wheels, a100 (MCDM)
Process completed with exit code 1.
Test win-64 / py3.12, 13.0.2, local, a100 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.12, 13.0.2, local, a100 (TCC)
The operation was canceled.
Test win-64 / py3.11, 13.0.2, wheels, rtx4090 (WDDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.11, 13.0.2, wheels, rtx4090 (WDDM)
The operation was canceled.
Test win-64 / py3.13, 12.9.1, local, l4 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.13, 12.9.1, local, l4 (TCC)
The operation was canceled.
Test win-64 / py3.12, 12.9.1, wheels, l4 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.12, 12.9.1, wheels, l4 (MCDM)
The operation was canceled.
Test win-64 / py3.14t, 13.2.0, wheels, a100 (MCDM)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.14t, 13.2.0, wheels, a100 (MCDM)
The operation was canceled.
Test win-64 / py3.10, 13.2.0, local, rtxpro6000 (TCC)
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Test win-64 / py3.10, 13.2.0, local, rtxpro6000 (TCC)
The operation was canceled.
Check job status
Process completed with exit code 1.
CI
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
CI
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
CI
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1842-push exists
Build linux-64, CUDA 13.2.0 / py3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-64, CUDA 13.2.0 / py3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-64, CUDA 13.2.0 / py3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-64, CUDA 13.2.0 / py3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-64, CUDA 13.2.0 / py3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-aarch64, CUDA 13.2.0 / py3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build linux-64, CUDA 13.2.0 / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build win-64, CUDA 13.2.0 / py3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, ilammy/msvc-dev-cmd@v1, mozilla-actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.14t, 12.9.1, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.11, 13.0.2, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Docs / Build docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167, JamesIves/github-pages-deploy-action@6c2d9db40f9296374acc17b90404b6e8864128c8, marocchino/sticky-pull-request-comment@67d0dec7b07ed060a405f9b2a64b8ab319fdd7db. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Docs / Build docs
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
Test linux-aarch64 / py3.14, 13.0.2, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.11, 13.0.2, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.10, 12.9.1, local, v100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.13, 13.2.0, local, rtxpro6000
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.13, 13.2.0, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.13, 13.0.2, local, rtxpro6000
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.11, 13.2.0, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.14t, 13.2.0, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.13, 13.0.2, local, h100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.13, 13.2.0, local, h100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14t, 13.2.0, local, h100(x2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.12, 12.9.1, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.11, 13.2.0, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.13, 13.0.2, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.10, 12.9.1, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14, 13.0.2, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14t, 13.2.0, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.12, 12.9.1, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14t, 12.9.1, local, t4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14t, 13.0.2, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14, 13.2.0, local, l4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-64 / py3.14, 13.2.0, local, t4(x2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test win-64 / py3.12, 13.2.0, local, a100 (TCC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test linux-aarch64 / py3.14, 13.2.0, local, a100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test win-64 / py3.12, 13.0.2, local, a100 (TCC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test win-64 / py3.13, 12.9.1, local, l4 (TCC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test win-64 / py3.10, 13.2.0, local, rtxpro6000 (TCC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors
sccache stats
0% - 0 hits, 0 misses, 0 errors

Artifacts

Produced during runtime
Name Size Digest
cuda-bindings-python310-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
6 MB
sha256:6c38ce2aa627d4e6f1aecb2a9180a16f596baa5296f9fabdc8decf47b21f17bf
cuda-bindings-python310-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
410 KB
sha256:bea37cea6dd8a3e6e73ab60c354ed9ac5373ede795cffe23e2f7cf7a0263eb6c
cuda-bindings-python310-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.43 MB
sha256:77067a02cc042874a675cebd135407e4edefc59a1fbf6bf0d46e1e20cc7f902b
cuda-bindings-python310-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
398 KB
sha256:aa8f5766ef6fd41026d00b3adbda6d001ae8b44413908896563a0ea2728c3282
cuda-bindings-python310-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
5.32 MB
sha256:b3849a093a785c5b28d00532d0a48565984cb1cdcf55df77e6cc14de797e5334
cuda-bindings-python310-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
63.2 KB
sha256:10c9f93a989a1e347216fee384999c42d5d497dfb61e8001b595eea666e395ee
cuda-bindings-python311-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
5.98 MB
sha256:10cba1ae3c0f5835e372f5c5497d981f0735b2265caec212a4bfe218e4a802c5
cuda-bindings-python311-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
432 KB
sha256:0d607dd39840c57cddbcc07e7391fa8f1e957fae5abc4ab653be9bed589364a6
cuda-bindings-python311-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.41 MB
sha256:ea10195d1a7cb80b537e83b44447528962b39f4b416740d77ee29a03a30c1553
cuda-bindings-python311-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
421 KB
sha256:753278c12c028ea7a2a4c606e4a40a4e214ee0a694c1c524c2f68a7cff32ec13
cuda-bindings-python311-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
5.36 MB
sha256:4c8ab4adb24d01def4ad04aaf59b81a1cec1650b9ac9ee30ace487c2b285bdb6
cuda-bindings-python311-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
63.5 KB
sha256:9a29af129067b5aa75cab4d4ec0f76f3e84b1619f8a3a3367c3a472874f6c553
cuda-bindings-python312-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
6.02 MB
sha256:b64357e57520bfdb143dd937e32aff64ffdfa372309646685b641a7323ca74a9
cuda-bindings-python312-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
438 KB
sha256:f395454db31b5dea9a37360d8a465e02c865845936f4d242cdb54965c5adc014
cuda-bindings-python312-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.42 MB
sha256:75938fab6d58d7f7e9fd97a0b652de6c199067f0e1ac47813c5a6b48b82b730b
cuda-bindings-python312-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
422 KB
sha256:47cfdd0f0336b5cee81d8a40300753497431cf70fc21c91e5f42267d3a513c7b
cuda-bindings-python312-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
5.53 MB
sha256:71bd0e1277ebc324c193ce11df0b849a9f45161c1561612adac99cd6926cc1e9
cuda-bindings-python312-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
62.5 KB
sha256:b55309254138d4d0fceb5f7dce99337afa24ee30aea563e203fcee8790b1dcd6
cuda-bindings-python313-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
5.84 MB
sha256:332e592e90f7ca08e428827fee7e6431146111e988db246ad867897e81f81e93
cuda-bindings-python313-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
448 KB
sha256:155a55d51e99b86778c7f5fe920b7d91562d5fbc9506956ff89a1fe4777fba29
cuda-bindings-python313-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.3 MB
sha256:430812bb9032d42909dbde5af56aa14dba2c3244e6a90ea028b8d854ef73f055
cuda-bindings-python313-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
430 KB
sha256:72995fd6291d512eebd20f76c8ff5ad108a6f6b95f01269d9247cf42912ad3a0
cuda-bindings-python313-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
5.49 MB
sha256:33c836f870ca8174e8adb6dda386d22d3a765340acda4ef15478bd915a150451
cuda-bindings-python313-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
62.1 KB
sha256:86ae11529ed2ff99a66b1a9e6351cdd8e7129c3dd1e3998d7d7c1648d271e62b
cuda-bindings-python314-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
5.88 MB
sha256:c10fcba98b3fa6a38122ea47c5b9d9d1fd016cc3988e032eb7a3d59a98ce429e
cuda-bindings-python314-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
444 KB
sha256:5d282f3d678d361c44112658666b4a8120a07c91b7c52cba5c9a6510c33e8d47
cuda-bindings-python314-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.39 MB
sha256:0aebce03022de987a0b76732ad6e1d4b9b1610b8411fe2ca2b53c7b5eb6a16ef
cuda-bindings-python314-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
429 KB
sha256:e83ece18135fc96f6a01f5ea84e79a83e31ce86ea06a4ce9a67d06bf8a5633e9
cuda-bindings-python314-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
5.59 MB
sha256:fd85c0e999a85ec81ad7cae58828e2ef51a3988502c42616107415e36a99a42c
cuda-bindings-python314-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
62.8 KB
sha256:5363530d7109871a0c63ca29c79dbf10e0c9d7afb19cc6bc9fa4cd8424318ae7
cuda-bindings-python314t-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
5.74 MB
sha256:f5f7a3546cb747f846a362cefef6594f44d2068344fb997341656893db2117b8
cuda-bindings-python314t-cuda13.2.0-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
462 KB
sha256:6e69241888622589212136be78eac0aeb4f7cf53a623d21a59ed10953538ab67
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
5.2 MB
sha256:656863d8e0e0e6d897e09f995bcb8ef02e62b8819da7582508ebf05dff610bf8
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
463 KB
sha256:6300e1fae5e4e8c59a75f7fec08f9f0fea309970fa10a9fad0689232bafbbd3f
cuda-bindings-python314t-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063
6.33 MB
sha256:30a1a32ccf57e7d6181358c0039fe41b8e1c38e8a78aa2165cdd375633eadde2
cuda-bindings-python314t-cuda13.2.0-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
74.7 KB
sha256:8d8bee783e0a0575f9e2b390b253847d1a675149647a9d14d73d276d7f4eb6da
cuda-core-python310-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
26.3 MB
sha256:50137f77c358576054b500e6f9968992ce43220d8ddbb8edbb0df15628e729e3
cuda-core-python310-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
113 KB
sha256:f814bb624f747b34f791da511d9b46b2d3037aa8dbde9075efbf16a2fd928955
cuda-core-python310-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
26 MB
sha256:d12f936413befc50d66dc856e72f3b2da001da5776bb781b580f6c6ef7ffc03f
cuda-core-python310-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
112 KB
sha256:6412b480e408268e24d2463e101da5be9564b576143a0b4cb236bebfaa580d3f
cuda-core-python310-win-64-237e67597ef2a53c5e448035009f4f27558e7063
3.75 MB
sha256:4209e4b32794e92c9c3895d3930a05a63ac238a8da9b57dd551576082b95aa1e
cuda-core-python310-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
25.8 KB
sha256:76ca6f34060707bb2160415dbd2e1320526bc22cf3a84d94b96b0f406e065f27
cuda-core-python311-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
27.6 MB
sha256:2c1f1f0cf98b4e05842222a7b90221c5775f96baa3539a7e303586b9780b652c
cuda-core-python311-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
118 KB
sha256:1d0bd1efa11183643143604e11f770ae6756ac0d3e04434cef946f42a2315c22
cuda-core-python311-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
27.3 MB
sha256:41b599d91b7469fff8474fd68396925c6b73418f867a3b3a963cf07aec123f8b
cuda-core-python311-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
117 KB
sha256:9b9ee25535f11070deb966e135b1adf91d988e9d27971423dc57145f9e4534be
cuda-core-python311-win-64-237e67597ef2a53c5e448035009f4f27558e7063
3.75 MB
sha256:82af3066739110c79648301d483a0f460e5b63c4e16a52b463a3c37d4b2b53e8
cuda-core-python311-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
25.9 KB
sha256:f94ce7ec6cd8f361887085ea957705b168168228cb07913273d982e700d32264
cuda-core-python312-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
27.8 MB
sha256:7b7eceadedf132d9f7bbae909f2aa41f54d393863c60ae130c3afe08eaf98daf
cuda-core-python312-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
124 KB
sha256:1ba41e89845da3be782258f1a7af282712e8309843018e767c51f73a5fd7585f
cuda-core-python312-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
27.3 MB
sha256:5e180d56153bafc6e02317eab79aee2c88aa817994014e41b1b2b1eb1a3909f1
cuda-core-python312-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
122 KB
sha256:efa5ee84465aef1f22c0931569ed2d82652eaaf1283dc84e5606cbf8d7eff540
cuda-core-python312-win-64-237e67597ef2a53c5e448035009f4f27558e7063
3.7 MB
sha256:89ea5d64532216f67f4834237311a44a28d150ce2b6728afa52ff6ee82f18746
cuda-core-python312-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
26.3 KB
sha256:7e7143fbc8a7f8b9a693ff96e681eac7bf13da9fde00fb57dc1e6ca95b2989a4
cuda-core-python313-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
27.3 MB
sha256:894b084bf89d16c91ce6021dad3ce13012febf1c1dd6e3987893a22d7247807f
cuda-core-python313-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
119 KB
sha256:8dc27c7dc7ab4b63ea7f996dba80e47119856eab5e57df0bc29f3c0555e8601c
cuda-core-python313-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
26.8 MB
sha256:c9fde93fb0064f409b311209d42fac196def1499de9856bf96123b9d46326ca2
cuda-core-python313-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
117 KB
sha256:718f5f235b1d974de7bf20e7457aef669b771039f14cd803a31e8d48120cd11a
cuda-core-python313-win-64-237e67597ef2a53c5e448035009f4f27558e7063
3.68 MB
sha256:a98b68c7eaed70b05aaadbc747a9be889d690e17396f1a0ec1627827d9e867c9
cuda-core-python313-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
25.7 KB
sha256:4ef7d21f98a9cc2fcaccc73b5491bfe5eaf42b10acfee40744780be22751d3bf
cuda-core-python314-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
27.1 MB
sha256:1bee14d17da559d1586e4820a63a95332b547b36473f22308b0be5c4cbb5ccaa
cuda-core-python314-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
118 KB
sha256:70c00547ee63ddef018a11699d99bae3681b563c987407bf85b5cc3b0ed6af46
cuda-core-python314-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
26.8 MB
sha256:23165fce5bd069252ad2c8e5f853b624bd7c0203554a379e5fe7443c91520a5f
cuda-core-python314-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
117 KB
sha256:66449f893cb3ca5308147d476ae37b8bb05b6eb977ae1f691b2a8999fd55495d
cuda-core-python314-win-64-237e67597ef2a53c5e448035009f4f27558e7063
3.78 MB
sha256:94b524e9646a2dcc7b94574c6b66932479765e8af11dcf76ee76ee090f77406d
cuda-core-python314-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
25.8 KB
sha256:54a787fa4e2237e7281c0886e95fe721d76a3dc9821dbb9c77c2b58d9f3487f5
cuda-core-python314t-linux-64-237e67597ef2a53c5e448035009f4f27558e7063
28 MB
sha256:cfed32050cc01b8d916dd38a5b3d0152ecfc0b6998ae476405962e198589893e
cuda-core-python314t-linux-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
142 KB
sha256:625aa7b3ff7ff4364b5f2b80e2d09724eb1f3f7e26dc00ae817cc991c5d1f3c1
cuda-core-python314t-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063
28.3 MB
sha256:337f9f03dee6743372eab0eaee244ad3efeb3d21100ac18a155503322dbd279f
cuda-core-python314t-linux-aarch64-237e67597ef2a53c5e448035009f4f27558e7063-tests
142 KB
sha256:f6f98136986db9ccfcdd525ca5cc0926702ebef35a2b4653e72d015b5dc46769
cuda-core-python314t-win-64-237e67597ef2a53c5e448035009f4f27558e7063
4.41 MB
sha256:7f86e70f19b06b75c3cab655e2ce1909edc7796301eb67cd275f287c6432a597
cuda-core-python314t-win-64-237e67597ef2a53c5e448035009f4f27558e7063-tests
29.2 KB
sha256:18fb622af6d428f61458d988efce9f12c7b72ce1a72d332e01bf0bb815af3b01
cuda-pathfinder-wheel
45.3 KB
sha256:bee09ad06b01c9f9324c6b204303b5f0446df08aa0ca3d44e63f8a2a4a492aba
cuda-python-wheel
7.78 KB
sha256:62940bc48cd63c28ff831e334669dacd04557c31ad9476db4c76342d588d5e76
github-pages
19.8 MB
sha256:2cace8e4b8c18606fa574eafeece6a7a8d32ac819cea88473594c73b0eaa1ced