Skip to content
CI

Suppress pip cache and root-user warnings in Linux container CI jobs #3031

Sign in to view logs

Suppress pip cache and root-user warnings in Linux container CI jobs

Suppress pip cache and root-user warnings in Linux container CI jobs #3031

Triggered via push April 7, 2026 23:25
@copy-pr-botcopy-pr-bot[bot]
pushed 1a0a753
pull-request/1879
Status Success
Total duration 1h 2m 36s
Artifacts 74

ci.yml

on: push
should-skip
6s
should-skip
ci-vars
1m 1s
ci-vars
Matrix: build-linux-64
Matrix: build-linux-aarch64
Matrix: build-windows
Docs  /  Build docs
9m 15s
Docs / Build docs
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

40 errors, 54 warnings, and 18 notices
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-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.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.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.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: 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: 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.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.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.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-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.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, 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-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.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.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.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.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: 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: 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.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.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.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-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.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.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.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.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
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: 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: 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, 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.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.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.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.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, 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.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.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.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.
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.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.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-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.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.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.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.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.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.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 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.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.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.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.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-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-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.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 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-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/
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-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.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.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.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.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.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-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.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.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.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 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.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 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 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 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 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 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/
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.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 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 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.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 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 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.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/
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-1a0a753bc289b28f781e77553518130e80e1192a
6 MB
sha256:425fb3d82281b8668a6aaccb9f6aa4ea8a8d4e0b7701644680e21b5b95856435
cuda-bindings-python310-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
410 KB
sha256:b91743571a03090e68826a72f4642d55ebddc1a78eb5da4c0065834fc0f5c6d0
cuda-bindings-python310-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.43 MB
sha256:b7292f64c14cbc3bdb491acc6f6f2702cf26f1e64c0d30a6ea8dd146cf770443
cuda-bindings-python310-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
398 KB
sha256:5a113440abea0eda745baf2dc2cf984e4b6504cbac10a94ade2d281b7e4a170e
cuda-bindings-python310-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
5.32 MB
sha256:23843bc950465bc623ce6a35adbdab7281cb3a95c4b4e022b78fa8e970350a56
cuda-bindings-python310-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
63.2 KB
sha256:e7742ae40d6ce058c1f8208ac41f81637625b10c4554694a33403db849e12e1d
cuda-bindings-python311-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
5.98 MB
sha256:b94f597a2f039b376d21b03c29c8104b5c5c833f14b65fdd78dac88f83f429fc
cuda-bindings-python311-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
432 KB
sha256:27b065e12308bc0a40b9ea755654ffe748c7ec8dcda72d88f5896a35708c2404
cuda-bindings-python311-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.41 MB
sha256:f8ca6bffe806ee1e5338372ee854012975241d30f3beddbd2fa0d85655ef29a2
cuda-bindings-python311-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
421 KB
sha256:6c72b17fdd68f4db5dc22df2e691c290ec93dfe11998a97c50710c32078ec851
cuda-bindings-python311-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
5.36 MB
sha256:1ab74d29a9e2490c9d70cd8c7808fa1a701dd1222667aa33023d145246a5cdd7
cuda-bindings-python311-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
63.5 KB
sha256:12e8d301b9cd5eacc6b9eaa58516ed8c0cd79d5c63088b1ffa130bd5198d27ce
cuda-bindings-python312-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
6.02 MB
sha256:9425544943ddf73e3c3383f84659ea9e99c7e87702ce45910500061551b83ac6
cuda-bindings-python312-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
438 KB
sha256:dc20b2a1d05b87cdc905798341b7f0c9d94d3dda093a8a6499321aabe04157f8
cuda-bindings-python312-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.42 MB
sha256:1fec7327716e13e146051706da554719e00b24009b0faaae8e074b83d6e8662b
cuda-bindings-python312-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
422 KB
sha256:71114d686bac07eb78321e8a8efd33369daff530af399af517ad95a3dcf4752a
cuda-bindings-python312-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
5.53 MB
sha256:490860c5bb7c32381aaa02797d727533f141dfedf1a856e8a614bee3cca9ac00
cuda-bindings-python312-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
62.5 KB
sha256:45c4dc4904635d31fd7ca8b0a79b0904f21e20da2cd2fbb06197d08b9a59aa42
cuda-bindings-python313-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
5.84 MB
sha256:c7ea4290d4db5cd70d161a908a94ad0db4fc905588884bf3b6f3efd0710c3e91
cuda-bindings-python313-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
448 KB
sha256:d3ed3e7ff96d04039586191a08502797769b9c735c297d95474168ab077e4477
cuda-bindings-python313-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.3 MB
sha256:0b694ab50730e9c512a0efc4ec878242e47f24160fc7017d619ae6741d527543
cuda-bindings-python313-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
430 KB
sha256:82e2abdda9a05a1d85dde050fe6af3e86a6206779c940085a64ba2fc04773078
cuda-bindings-python313-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
5.49 MB
sha256:4ca3397920910ce3242d9d1bdf6107130e8c0ad1082f4761d15d0b77a5d1094e
cuda-bindings-python313-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
62.1 KB
sha256:97eee435ebcb20fa33c4c7d9fe27762724481b735dd33a8927a6d2d55f728586
cuda-bindings-python314-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
5.88 MB
sha256:cb4cd33486c4faa8b1c1d4c9b07f5f2c2db9d37b0c73865d37d1da71468aa2eb
cuda-bindings-python314-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
444 KB
sha256:fa9959edf419499841ac848c6043b32ac84d863d7b14fbef12db692564965632
cuda-bindings-python314-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.39 MB
sha256:f81f56140ae2706d301f4170434c5705c29da53b48bbee801a3eed4369399078
cuda-bindings-python314-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
429 KB
sha256:2d845f139503ab95094ed964e7431933686d19be947a4d6d506e1c36d375e973
cuda-bindings-python314-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
5.59 MB
sha256:a95afdf5b643c321d47308c09a8e41a07b7a273d8c27cce211e01d7509a8d2aa
cuda-bindings-python314-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
62.8 KB
sha256:b6f9c757119b43e930d967879b68edecf51d3728edac3620888f477e4f192b3b
cuda-bindings-python314t-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
5.74 MB
sha256:55f290a6a122f324e5f1a78472d51894715131d1b4a217225d3f3c763e8b1a3d
cuda-bindings-python314t-cuda13.2.0-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
462 KB
sha256:92a8b625772aa4af300fe88b503420b76c1935e67fa627cf56128f879eb62d8f
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
5.2 MB
sha256:6eb901909c7af01b834dad615df63a7ba6c7c2c935962244c93e50a66e178963
cuda-bindings-python314t-cuda13.2.0-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
463 KB
sha256:a1416fb3b8426a785093761e0e24a593ab700b001850433a10fd249a9b2f7c9c
cuda-bindings-python314t-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a
6.33 MB
sha256:8c19c7b33bc63f12c599541b290e86d4160ebfedaa33955b1c3537f3f2dc3c4f
cuda-bindings-python314t-cuda13.2.0-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
74.8 KB
sha256:736df7a95257119494cb30d0887d960d5cabc3d49bf1f33a518830787ee53a58
cuda-core-python310-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
27.7 MB
sha256:47ebe72121653e14a36bb10b626a820d917df40ad84573381fc1462d7cd6f0a9
cuda-core-python310-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
113 KB
sha256:0e49b527404dbb1dbdfc3149a5b2fd931e8e3493fddff7e73291b498d9878886
cuda-core-python310-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
27.4 MB
sha256:dce3c136f2bcae3841b1b881018adf3bb10b4dbf70db8120507ada839f4850ac
cuda-core-python310-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
112 KB
sha256:508c449f16067b3a0323c6e7bef50c924bf45ce5dc7807f1e7738c218a21a909
cuda-core-python310-win-64-1a0a753bc289b28f781e77553518130e80e1192a
3.94 MB
sha256:4cabf3480e533d1b78b70beca34bd1b08568eeabdc9577e0e90a9c9b07d729a5
cuda-core-python310-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
25.8 KB
sha256:1dbee396b1e6fc4f208c5d254a22de583af905bd23e4b9bd15d8e3be00de398c
cuda-core-python311-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
29.1 MB
sha256:4c3b6bf2e544076a34759fa30cf47ec4303e734880229c4c4225f1cac206ec58
cuda-core-python311-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
118 KB
sha256:5cd2e9a42e5710e96890599bdecdb52f36c98f0b604f1d6cdc456371e5caf71a
cuda-core-python311-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
28.8 MB
sha256:84262744c211925a8eea0306ee9263a85ace0e88c0b52896c0358f6be43c21d8
cuda-core-python311-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
117 KB
sha256:7e6a14586b4ec20bdcb51530330611e711ed2204a9f0946b868d0b08fdf44ed6
cuda-core-python311-win-64-1a0a753bc289b28f781e77553518130e80e1192a
3.94 MB
sha256:9ee917c265d6bf0952c98c571181690da0f5f0fd51bd45ff20f2d16f084fe8a6
cuda-core-python311-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
25.9 KB
sha256:a5ecec5bb02d4dc96b1a90b6c8e88868bc2e9a125984b1d2409b63a6194c808d
cuda-core-python312-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
29.3 MB
sha256:bbaad2a3522e4c388eec3a15f42d161ad2924cfbbcc404e0c40fca301bf85b7e
cuda-core-python312-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
124 KB
sha256:d6d00303114a745c0a798e79eb2a4465b370de4dc825952566c58cd5b8da94ad
cuda-core-python312-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
28.7 MB
sha256:c6cb0ef6189600cb8236bab8d5e8f7c597a65379412ee3d5343c76db881e3a9a
cuda-core-python312-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
122 KB
sha256:b9e42286cf957ff1526ccdf65859a9c7f3292df930ce589e67df7fbf3c83b93c
cuda-core-python312-win-64-1a0a753bc289b28f781e77553518130e80e1192a
3.89 MB
sha256:f7a8766a6c265dc8e7179e00cff52653242031c643053b3a318def5958293703
cuda-core-python312-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
26.3 KB
sha256:99da955b4aa3a718ede400d8e245af4ad3b94b48ebc2fa11d361db188ad0accc
cuda-core-python313-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
28.8 MB
sha256:6b2fc67f18b68fe8700947bfc7387f84684615fcbeb8396da6de7c980f8eb5b0
cuda-core-python313-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
119 KB
sha256:70d37056130a5aeec58ee13a7edd38578206ed3cf166fdd82f016261d486626d
cuda-core-python313-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
28.3 MB
sha256:b2cc64ff04decbbee2768b1ef2eed1b8bafe15e27635c0aefd0f17164a898677
cuda-core-python313-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
117 KB
sha256:139345f341cbfb873aead87356d2ad147819218b32b59a9826458466a696a342
cuda-core-python313-win-64-1a0a753bc289b28f781e77553518130e80e1192a
3.87 MB
sha256:6fca12276cdf176f291e42de6682966ef2e36c27096887007f690e8a3a660897
cuda-core-python313-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
25.7 KB
sha256:95e55c909b5a725999b84cd7a433d4f3637e96d4afe965a780fe98e9470d24b9
cuda-core-python314-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
28.6 MB
sha256:9be87bb959e823e5c5440519ca7481e40350b3ecff6ef4317ebca303c1aff397
cuda-core-python314-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
118 KB
sha256:4de2d5f11143849ee02f09e84f6b1e1237240333118dc73927e9a32f6884da11
cuda-core-python314-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
28.3 MB
sha256:382dc0c804ebe686e48bf1bd631d38b56e43a825e5263dd891548b885160fe6d
cuda-core-python314-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
117 KB
sha256:0b48fe05710ca6f2dfda8cb4e5140120e66488ab99b7a8ada8dc00da582bb8d9
cuda-core-python314-win-64-1a0a753bc289b28f781e77553518130e80e1192a
3.97 MB
sha256:08f6ebf49c203984a0beb42782323237162e0842df468e104e2b2be896108c9f
cuda-core-python314-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
25.7 KB
sha256:296ed784bd3cbc8c2b07958608a788eb37e0a7f12d6d06f7497e6973fd87b351
cuda-core-python314t-linux-64-1a0a753bc289b28f781e77553518130e80e1192a
29.5 MB
sha256:d8968423c3bbc1e69ed4fb207f1cd047f5aee855d9fa62e01eddf2ee4941425d
cuda-core-python314t-linux-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
142 KB
sha256:10f9dcc97cf246278889ada8228fb174344e1dc8426c427be1243de7e3803757
cuda-core-python314t-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a
29.9 MB
sha256:fbb67da5ae164a6d8af988a3aba9cbc75ee0ecd20ed52313754a8733de6b802f
cuda-core-python314t-linux-aarch64-1a0a753bc289b28f781e77553518130e80e1192a-tests
142 KB
sha256:e1f658b6f508d099a4aef09fa06d9b3378c8bb8813b1820f77a977fb54a9dc8a
cuda-core-python314t-win-64-1a0a753bc289b28f781e77553518130e80e1192a
4.64 MB
sha256:533d2dcd3fee95096c553f6a342180eedefb7f3b81a922db4df4c2f71858ede3
cuda-core-python314t-win-64-1a0a753bc289b28f781e77553518130e80e1192a-tests
29.2 KB
sha256:a4cd4dfa6bc5b370e92d47ea126fb78922f386c99da84d8e8395e5dfb41c20be
cuda-pathfinder-wheel
45.5 KB
sha256:2cea840140dcf2dea698d45903620aafce74aca031d9a4e09fb3cade72077228
cuda-python-wheel
7.78 KB
sha256:23dcf2921cea25c2c9cdebd0a4e2ed5a71fd01a189758eb498b6f445c1530b55