Skip activation checkpointing compile test on CPU (#1917) #2567
Titus-von-Koellerpython-package.yml
on: push
Matrix: build-cpu
Matrix: build-cuda
Matrix: build-rocm
Matrix: build-xpu
Matrix: build-wheels
Matrix: audit-wheels
Create release and upload artifacts
Publish wheels to PyPI
Annotations
52 errors and 45 warnings
|
build-cuda (ubuntu-22.04, 12.0.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.5.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.5.1)
The operation was canceled.
|
|
build-cuda (ubuntu-22.04, 12.3.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04-arm, 12.9.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04-arm, 12.9.1)
The operation was canceled.
|
|
build-cuda (ubuntu-22.04, 11.8.0)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 11.8.0)
The operation was canceled.
|
|
build-cuda (windows-2025, 13.0.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.8.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.8.1)
The operation was canceled.
|
|
build-cuda (ubuntu-22.04, 12.9.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.9.1)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.4.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.4.1)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.1.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.1.1)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.9.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.9.1)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.8.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.0.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.8.1)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.0.1)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 7.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 7.1)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 7.2.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 7.2.1)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 6.3.4)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 6.3.4)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.5.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.5.1)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 6.2.4)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 6.2.4)
The operation was canceled.
|
|
build-xpu (windows-2025)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-xpu (windows-2025)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 7.0.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 7.0.2)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.3.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.3.2)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.2.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.2.2)
The operation was canceled.
|
|
build-cuda (windows-2025, 11.8.0)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 11.8.0)
The operation was canceled.
|
|
build-cuda (ubuntu-22.04-arm, 13.0.2)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04-arm, 13.0.2)
The operation was canceled.
|
|
build-cuda (windows-2025, 12.6.3)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (windows-2025, 12.6.3)
The operation was canceled.
|
|
build-cuda (ubuntu-22.04, 12.1.1)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cuda (ubuntu-22.04, 12.1.1)
The operation was canceled.
|
|
build-rocm (ubuntu-22.04, x86_64, 6.4.4)
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-rocm (ubuntu-22.04, x86_64, 6.4.4)
The operation was canceled.
|
|
Python package
Canceling since a higher priority waiting request for Python package-refs/heads/fix/issue-1904 exists
|
|
build-cpu (ubuntu-22.04-arm, aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cpu (ubuntu-22.04, x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cpu (macos-15, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cpu (windows-2025, x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, ilammy/[email protected]. 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-xpu (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.5.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.1.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.6.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.4.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.8.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.4.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 13.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 11.8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.6.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.5.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 12.3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04-arm, 12.9.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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-cuda (ubuntu-22.04, 11.8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (windows-2025, 13.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (ubuntu-22.04, 12.8.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (ubuntu-22.04, 12.9.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (windows-2025, 12.4.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 12.1.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 12.9.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 12.8.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 12.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-rocm (ubuntu-22.04, x86_64, 7.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-rocm (ubuntu-22.04, x86_64, 7.2.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-rocm (ubuntu-22.04, x86_64, 6.3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (windows-2025, 12.5.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-rocm (ubuntu-22.04, x86_64, 6.2.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-xpu (windows-2025)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-rocm (ubuntu-22.04, x86_64, 7.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (windows-2025, 12.3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 12.2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (windows-2025, 11.8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (ubuntu-22.04-arm, 13.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-cuda (windows-2025, 12.6.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ilammy/[email protected], Jimver/cuda-toolkit@6008063726ffe3309d1b22e413d9e88fed91a2f2. 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-cuda (ubuntu-22.04, 12.1.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-rocm (ubuntu-22.04, x86_64, 6.4.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_11.8.0
Expired
|
1.57 MB |
sha256:4f096dd891e209943e6b3d85747b5cd0306b792dc30d8496fe2b4c6e58a633db
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.0.1
Expired
|
1.53 MB |
sha256:db93e3345b899c2b33a0ff250270a978a0a201d3d8de1baba19559bcd3af7047
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.1.1
Expired
|
1.53 MB |
sha256:dd9714c26536834478d1ad5654492f6404e31a48b44d75104ecbde62a8576d63
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.2.2
Expired
|
1.53 MB |
sha256:284adb8fabeb1a5696ed7015d0bd6000fc3b09baf32cb5dceeb1dcaed4070711
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.3.2
Expired
|
1.54 MB |
sha256:25a120b538f804f047414515f9ff69e835e6d25c05ddb36bb05dedfc2555d824
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.4.1
Expired
|
1.54 MB |
sha256:f066637b50d5aa1ca014bb1de78387d18d41df466180e2ca4215f89cc07753ce
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.5.1
Expired
|
1.54 MB |
sha256:ca4929c038ebfb0acaa0d70f323ec55841d7e3cd3f2ba9449b0303cdb03d198c
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.6.3
Expired
|
1.55 MB |
sha256:c82e1dbe7328c7ed305750ce93225241cfd9f01cc11c8c35914b93e1e09dffa6
|
|
|
shared_library_cuda_ubuntu-22.04-arm_aarch64_12.8.1
Expired
|
2.4 MB |
sha256:864e3b8a3f9c553b38500cb357bde3d3bbc6ceb1eb8631d54b1e7dd8ba9a060d
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_12.0.1
Expired
|
3.1 MB |
sha256:3a9ed5d449d2d9733615989dfdf6355b5eadcd0035c8e66638cfe31569c6f484
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_12.2.2
Expired
|
3.1 MB |
sha256:c03203b123d6fe0198f77f801b1a79cca74698ccd915ff9b3526d3cd3580b4db
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_12.3.2
Expired
|
3.1 MB |
sha256:59bc22ce6fef083fc0c75af1e5798841f1056cc82c866c9105174f7b71e38fbc
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_12.4.1
Expired
|
3.09 MB |
sha256:eafcf8bf9b147f99c2ee7a5725f6ef95cf941c904d6630e5326a7e5f1865ca8b
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_12.6.3
Expired
|
3.1 MB |
sha256:2224e9b68d0a4383783964069520759abe4bcffa7ecc181e4bb43274c67879a7
|
|
|
shared_library_cuda_ubuntu-22.04_x86_64_13.0.2
Expired
|
1.93 MB |
sha256:351318caeee84462e9cdaf9bf08f5ffb3a2ae48aafef645fea30369ba813cdcb
|
|
|
shared_library_cuda_windows-2025_x86_64_13.0.2
Expired
|
1.89 MB |
sha256:c757b394c113ce9789a5c872847a4202a4d7b4aa2d51adf7a5bf829c8a749d1d
|
|
|
shared_library_macos-15_arm64
Expired
|
6.76 KB |
sha256:d59980b4ee8ae8d10d64a205b1c61bea8a19a0012841a89b046cc5bfb7641ec0
|
|
|
shared_library_ubuntu-22.04-arm_aarch64
Expired
|
10.1 KB |
sha256:560b376d0bf3906174cc15a290ce7c91260fd862c73189f20cc53e7c9095b28d
|
|
|
shared_library_ubuntu-22.04_x86_64
Expired
|
22.6 KB |
sha256:206288a3e1c598abdf3380ad0e6fa86c65360ba4928d5970d05820eb05370ee2
|
|
|
shared_library_windows-2025_x86_64
Expired
|
12.2 KB |
sha256:ef2db844e2eed45a5bf02f34cec07632fd16ece5bca7aa665e90088667d525aa
|
|
|
shared_library_xpu_ubuntu-22.04_x86_64
Expired
|
160 KB |
sha256:fe38c35b37c32bb79cf14949e29a63c4f502f9dd7cd55196d3d850d66ac79b5f
|
|