Skip to content

refactor(pathfinder): unify dynamic-lib subprocess probing (productio… #2752

refactor(pathfinder): unify dynamic-lib subprocess probing (productio…

refactor(pathfinder): unify dynamic-lib subprocess probing (productio… #2752

Triggered via push March 18, 2026 02:05
Status Failure
Total duration 36m 14s
Artifacts 74

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
2s
Check job status
Fit to window
Zoom out
Zoom in

Annotations

81 errors, 53 warnings, and 18 notices
Test linux-64 / py3.13, 13.0.2, local, rtxpro6000
Docker start fail with exit code 1
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.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-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, 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-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.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.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.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.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.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.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-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.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 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-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.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-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, 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.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, 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.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-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-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-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.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, 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-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.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-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-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-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-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-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.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-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 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 win-64 / py3.13, 13.0.2, wheels, rtxpro6000 (MCDM)
Process completed with exit code 1.
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-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.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
Check job status
Process completed with exit code 1.
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.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.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-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-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-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-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.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.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 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. 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. 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. 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. 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. 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. 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.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.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.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.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.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.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 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-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-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.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.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, 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/
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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. 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-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.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-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.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-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-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/
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-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 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 win-64 / py3.14, 13.0.2, local, l4 (MCDM)
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 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-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 win-64 / py3.11, 12.9.1, local, v100 (MCDM)
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.14, 13.2.0, local, l4 (MCDM)
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.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 win-64 / py3.14t, 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/
Test win-64 / py3.10, 13.0.2, 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-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.97 MB
sha256:21445860d261604c09f79a65b7f17b6196cac0a6a031c3f4f7993db968ced5ee
cuda-bindings-python310-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
410 KB
sha256:1af7387bdb82c5902f2e9a6ac2fd4daadd570f3e1c5c0a6a97b72ec7c98d8331
cuda-bindings-python310-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.4 MB
sha256:33436951a1d8542affd5cf0e73358a74997e8e860dc2a1853235859d3d78a936
cuda-bindings-python310-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
398 KB
sha256:d286b20b096fe9db1b1585b58af1c6c77e187f9f56b90c1e73622cd5decfcf2d
cuda-bindings-python310-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.29 MB
sha256:dc274b77a0eba073e54e54b9104a014253097423ffab361e49c63fc61bdbc173
cuda-bindings-python310-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
63.2 KB
sha256:8c0e9d7c9c0e350cbae6b3d4555e72f7a620be1498dd911e8e3934fd637754cb
cuda-bindings-python311-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.95 MB
sha256:6f83c877570d028d73e62e3edd509baa97fe047cac573860d0535ff9b34b39d1
cuda-bindings-python311-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
432 KB
sha256:31d90c06ecc95947078edd04065e428647842779ba1f231d1120b225c7f8600c
cuda-bindings-python311-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.39 MB
sha256:6d81b8e077995c69f79468b361068c3a1ae38fb1f778dec7ce78b167bcecb901
cuda-bindings-python311-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
421 KB
sha256:4e6ef3bcc08dd1eea128732398c99496d83b52fd1ea69aa5bb3317884b0e3bdb
cuda-bindings-python311-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.32 MB
sha256:3e37a80b6965ecad17168399e28630d281f5ed11da1858aa5ae96c3f8293d084
cuda-bindings-python311-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
63.5 KB
sha256:d0dd41a783e3a64cd936797ee05b4d28c99882b4284f3e583fe68c13eec205da
cuda-bindings-python312-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.98 MB
sha256:a5ca7d81201e6732a235c14fdb6299d9c0ca6b6f436a5f5e420796d7805c0d56
cuda-bindings-python312-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
438 KB
sha256:545b0f4d5d391089367e9a84fc18ef83953e300dcf9022e181b3c0c186e0cb67
cuda-bindings-python312-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.39 MB
sha256:c166f093a6ec3845dffe2c033f55b4a3672c6233fc4f29d3bdc5d838635e1933
cuda-bindings-python312-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
422 KB
sha256:9a57d35a308e132cd95b2a4ea099a55227aad929abfd87cbe7351aa71e32192a
cuda-bindings-python312-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.49 MB
sha256:2aaaeacf83f9a1b6652ed0de169608034a964a3fac59506e6bb9ed36d211a81c
cuda-bindings-python312-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
62.5 KB
sha256:09746d37a00c49d1973f4c2c7ed729d251f64274bc823b114d241088656dec24
cuda-bindings-python313-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.81 MB
sha256:240e5debd3feb4719ee84ca507041842a3a4b6a5ab974e5f29617beb41315226
cuda-bindings-python313-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
448 KB
sha256:927f125e0ca1d17f8fd73780d60bc37d2467a48740627d4038f8040714d2dfa3
cuda-bindings-python313-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.28 MB
sha256:e3ae065f2aca5c37cb6f39ca5d0de7de70b13d6a1fd48ea8c08d438635a49319
cuda-bindings-python313-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
430 KB
sha256:7242131fe3d3674ca162c9a47dbc66836ef24066c2c20a6cb69d96324cb65819
cuda-bindings-python313-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.45 MB
sha256:2ae1614091018300b5b73f0077deb4ac9c9b27c624d3e08c7c6ccf1b1cc764d8
cuda-bindings-python313-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
62.1 KB
sha256:15e651061c59a36962725231253a1b5efe351b45a36822299582e7e5ab02bb9f
cuda-bindings-python314-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.85 MB
sha256:963f9e3b4e7d991108413ad56f18f4e9adb8effb3e57aa62e71737c4a9585c1a
cuda-bindings-python314-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
444 KB
sha256:20ed06ea88a576bb4d4039bf4aa23b30c21df5727bfd523424ae59b6e1967205
cuda-bindings-python314-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.37 MB
sha256:70bf3d4b8eec558f81a653fa6ba225c39201973558e2a507ac702f351e3bb679
cuda-bindings-python314-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
429 KB
sha256:ddc8914697dd1fbebe1f95a0a18ced7dc77acbc30333d66f52aa33f6b7ac01cc
cuda-bindings-python314-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.56 MB
sha256:9c352cbc44ca320db881f34c818faee7b29745d1c26fdcb43b8e99564112b7a9
cuda-bindings-python314-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
62.8 KB
sha256:1cb7ae3af6beec5d94004de5a65291c92ffafde20446fdfd2745114e6c3b66d3
cuda-bindings-python314t-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.71 MB
sha256:412079626d6209d72e3f3bfe889c20dc1b011d03be7b5e7534f57bedf94b7675
cuda-bindings-python314t-cuda13.2.0-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
462 KB
sha256:1b67ab95b9c64981c6bdee2bed1fb6d995df41d3356cd92fd6f61e40eee48939
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
5.18 MB
sha256:2f3b9780db808b5908a24111bcc14fd66d88c808043dc4adf2264d65721b36a7
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
463 KB
sha256:c5238b3f53ae4c05a6cc028a70e0a8d065fc6d4107f7e73514f07b58d5cbd944
cuda-bindings-python314t-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
6.29 MB
sha256:36b5bce574fb0302bd9f74131353a1bf6499811a8ab96c890b7d15eb853d53fd
cuda-bindings-python314t-cuda13.2.0-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
74.8 KB
sha256:b0e2a8110075f723a26dfefe22c8b95c35b0aa1f14ef9e414de5fbdf773ff82e
cuda-core-python310-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
24.9 MB
sha256:f2b9d55106c1b2e6c59ca1bbffd972cfeb4d642dcc7e873a48a1634dd6e3358c
cuda-core-python310-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
113 KB
sha256:813f030925a9ecb5f3ec45369a6671d2c784a13cc396d5633d9ab829986d49bc
cuda-core-python310-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
24.6 MB
sha256:2f7cd5f7fe613efbb3f886c8a6bfb82cd67e4ef46086371b4dc98095777742ec
cuda-core-python310-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
112 KB
sha256:52cf6698d2fe3cc8e064d6ae2b31bc3e4bf0a4e2d79abb9039ba3786a1f304c0
cuda-core-python310-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
3.55 MB
sha256:e94c2c1ac022fa7e125147701c06cf1da3aa5d41c7e2335cccb7edd9cec07e4a
cuda-core-python310-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
25.8 KB
sha256:22d05b9407c8a8e1ab6d5d7d6c41271519ca127c7a9b4e387a614f758d77ec8e
cuda-core-python311-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
26.1 MB
sha256:934033f1956936ffb086c0e8838472928ec39af8a6fe0307dc35dd29abdddf54
cuda-core-python311-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
118 KB
sha256:49fae0727ab7fc2b53092f3e656446d39d5288a448c26cf6a6626721f18bb6c4
cuda-core-python311-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.8 MB
sha256:c93c7929eaef9c2d6239a37e84ebdac9b325cea4103721e397a41e3f34db5e2c
cuda-core-python311-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
117 KB
sha256:fc9a6a1a9b0c5f40ed8f17cc0f675bce3f0abd8c6471190e936c35e099aff202
cuda-core-python311-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
3.55 MB
sha256:a80c65a344037841931a63ef999e89dcb68c88be97326a3cc5fcdaf13bc28881
cuda-core-python311-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
25.9 KB
sha256:aaf35ca69a5ff148f109b00354c0f6fe81f87cdc72cb31cda96b76fcde7c57e3
cuda-core-python312-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
26.2 MB
sha256:31f2902f35d8334fc4f2095cf0043b01a4e7dd3648e5893b5c8b3a56d52a3d48
cuda-core-python312-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
124 KB
sha256:27049540490dfb79d0f716a810ba963e0e4abb4cf767f4b62e4287a546562ac9
cuda-core-python312-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.7 MB
sha256:5bb048e612a87d5526f34e784525e6c4299fc0df3c4c2f9a66fa7fee2c91510a
cuda-core-python312-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
122 KB
sha256:7adce3852d11582a10e72fc91f5869d9381d5c0979b1c065aab8bd4c483627a2
cuda-core-python312-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
3.51 MB
sha256:459ca221e74e6557a786c6f6836a72f171e193764fad8014f8f92530d8c5adfd
cuda-core-python312-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
26.3 KB
sha256:b29dece4177274abe6b326f74d057498b8dca997bf9b90a7b8d2831894aee884
cuda-core-python313-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.7 MB
sha256:5808bed9b828114d2a085ff58cf29e0dd5d75d605f346e6ddc29fbb24c96672c
cuda-core-python313-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
119 KB
sha256:0eb08f84a0847cff158033fc527ae902c1370614550b4d2532b63151ba002d94
cuda-core-python313-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.3 MB
sha256:64e24d60cefba7f1ec0bb23ab57b2018b943682bcb514e922f89c7adba250573
cuda-core-python313-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
117 KB
sha256:407b4248114f379ef015f3c5a0707e275914ab01c03b9d2ed4f4c01929ad1590
cuda-core-python313-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
3.49 MB
sha256:1db26bfbd150171d8ff6a4379d8f0973b8d7c516d85d1d2f4de8cbc4302a0e7a
cuda-core-python313-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
25.7 KB
sha256:3c534ab023327f1f9bc5b93b8e5e633686f521e7fb7c234d2c276e66958d99db
cuda-core-python314-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.6 MB
sha256:9319f2cbe3f300e2190aeb34c8b4be0d780d20c2bea90ed7ab75095b034cf291
cuda-core-python314-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
118 KB
sha256:037a324350fff8fb0d5f83ff73e893bc1a4d30db36317abcba31ca49ebcc8c22
cuda-core-python314-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
25.3 MB
sha256:85f84d1ee3e4449072b7f10b26ef9d754aee26f95ceab85afa124d4820b27ab6
cuda-core-python314-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
117 KB
sha256:8340c455fcfa67f0a40c2b73b4656f0b08ad8fa6365b7cc0c80ed471cb0083df
cuda-core-python314-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
3.58 MB
sha256:e1ce66164a4d62c8affb68469a19f8b90f7eec577502363ab452fa3bb7891e01
cuda-core-python314-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
25.7 KB
sha256:7b6bb4b580727de5651e92dedbbf2a80bd507f33654bf593877ec8de574ee8c3
cuda-core-python314t-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
26.4 MB
sha256:daa0f43076bbe4274fe16626137b3da7951170388ca661da2a899edd2b6a8e35
cuda-core-python314t-linux-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
142 KB
sha256:33fd5d1ee8b2413100f3dec67f0a17e124ef09fc163ac557f71374ed7650949b
cuda-core-python314t-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
26.7 MB
sha256:af92019c95ff3d1ba19d70ecfdee5af2029676f2dd77e0505d02ca0813920088
cuda-core-python314t-linux-aarch64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
142 KB
sha256:2f582c504291cbbc6c5bbf5cace99f368f20727caf410e2fbfbe4840e0ffc7c8
cuda-core-python314t-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629
4.18 MB
sha256:95f8ee93671424acd9026b4174780fc5641dc52e459d14b098c7efa561d02e8d
cuda-core-python314t-win-64-69d3a1f4e1031bffe02848c7f3b9ca95b01c1629-tests
29.2 KB
sha256:240a146ded2a018738873bf543e0de1d1dab2a0c1204557bafad588d61a65d56
cuda-pathfinder-wheel
43.9 KB
sha256:fc57f9f797995e704616dbb4037ba45de39bd6eb36687a158436a3e72f8b62f2
cuda-python-wheel
7.77 KB
sha256:3c8705861553e016458782cbaba51411cdbec9528173f45f12ea9e3da94767db