Merge branch 'main' into stackable_ctx_data #20136
copy-pr-bot[bot]ci-workflow-pull-request.yml
on: push
Build workflow from matrix
28s
Matrix: dispatch-groups-linux-standalone
Matrix: dispatch-groups-linux-two-stage
Matrix: dispatch-groups-windows-standalone
Matrix: dispatch-groups-windows-two-stage
Waiting for pending jobs
Verify Dev Containers
/
Verify devcontainer files are up-to-date
31s
Build MatX (optional)
/
Notify Slack of MatX failure
Build PyTorch (optional)
/
Notify Slack of PyTorch failure
0s
Matrix: Build RAPIDS (optional) / build-rapids
Matrix: Verify Dev Containers / verify-devcontainers
Build RAPIDS (optional)
/
Notify Slack of RAPIDS failure
0s
CI
2s
Annotations
114 errors, 54 warnings, and 1 notice
|
cudax nvcc Clang / [CTK12.0 Clang14 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.0 GCC9 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.0 GCC9 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.0 GCC9 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++20] Build(arm64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++20] Build(arm64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++20] Build(arm64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang18 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang18 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang18 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang17 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang17 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang17 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++20] Build(arm64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++20] Build(arm64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++20] Build(arm64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang16 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang16 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang16 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / Bk / [CTK13.1 Clang20 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / Bk / [CTK13.1 Clang20 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / Bk / [CTK13.1 Clang20 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.9 GCC9 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.9 GCC9 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.9 GCC9 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK13.1 Clang19 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK13.1 Clang19 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK13.1 Clang19 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++17] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++17] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++17] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / Cs / [CTK13.1 GCC14 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / Cs / [CTK13.1 GCC14 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / Cs / [CTK13.1 GCC14 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
cudax nvcc GCC / [CTK13.1 GCC12 C++20] Build(amd64)
Process completed with exit code 1.
|
|
cudax nvcc GCC / [CTK13.1 GCC12 C++20] Build(amd64)
To replicate this failure locally, follow the steps below:
|
|
cudax nvcc GCC / [CTK13.1 GCC12 C++20] Build(amd64)
🏗️ Build CUDA Experimental - Failed (⬆️ click above for full log ⬆️)
|
|
Test CPU-only import
Unable to download artifact(s): Artifact not found for name: wheel-cccl-linux-amd64-py3.13
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
|
Build RAPIDS (optional) / rmm ucxx raft cugraph
Process completed with exit code 1.
|
|
Build RAPIDS (optional) / rmm ucxx raft cugraph
To replicate this failure locally, follow the steps below:
|
|
Build RAPIDS (optional) / rmm ucxx raft cugraph
Failures: cugraph
|
|
Verify and summarize workflow results
Process completed with exit code 1.
|
|
CI
Process completed with exit code 1.
|
|
Build RAPIDS (optional) / rmm kvikio cudf cudf_kafka
Process completed with exit code 1.
|
|
Build RAPIDS (optional) / rmm kvikio cudf cudf_kafka
To replicate this failure locally, follow the steps below:
|
|
Build RAPIDS (optional) / rmm kvikio cudf cudf_kafka
Failures: cudf
|
|
Build workflow from matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
|
|
CCCL Packaging nvcc GCC / [CTK13.1 GCC14] Install(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
CCCL C CUDASTF nvcc GCC / A / [CTK13.1 GCC13] Build(amd64): sm{75}
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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 documentation
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. 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/
|
|
CCCL Packaging nvcc GCC / [CTK13.1 GCC14] Test(amd64, RTX2080): sm{75}
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
CCCL Packaging nvcc GCC / [CTK13.1 GCC14] Test(amd64, RTX2080): sm{75} -min-cmake
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
CCCL Packaging nvcc Clang / [CTK13.1 Clang20] Test(amd64, RTX2080): sm{75}
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
CCCL C CUDASTF nvcc GCC / A / [CTK13.1 GCC13] Test(amd64, RTX2080): sm{75}
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.0 Clang14 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.0 GCC9 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.0 GCC12 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++20] Build(arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang18 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.9 Clang14 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.0 Clang15 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang17 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.0 Clang20 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang20 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang15 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.1 GCC14 C++20] Build(arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang16 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.1 GCC11 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / Bk / [CTK13.1 Clang20 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.9 GCC9 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK13.1 Clang19 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.0 GCC11 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc Clang / [CTK12.9 Clang19 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++17] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK12.9 GCC14 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / Cs / [CTK13.1 GCC14 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.0 GCC14 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc GCC / [CTK13.1 GCC12 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. 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 CPU-only import
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
cudax nvcc MSVC / [CTK12.0 MSVC14.39 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc MSVC / [CTK12.9 MSVC14.44 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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 RAPIDS (optional) / rmm ucxx raft cugraph
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5. 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/
|
|
cudax nvcc MSVC / [CTK13.0 MSVC14.44 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
cudax nvcc MSVC / [CTK13.1 MSVC14.44 C++20] Build(amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. 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/
|
|
Verify and summarize workflow results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/github-script@v7, marocchino/sticky-pull-request-comment@67d0dec7b07ed060a405f9b2a64b8ab319fdd7db. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build RAPIDS (optional) / rmm kvikio cudf cudf_kafka
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5. 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 PyTorch (optional) / Build PyTorch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5. 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 MatX (optional) / Build MatX
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5. 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 RAPIDS (optional) / rmm ucxx raft cuvs cuml
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5. 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/
|
|
Verify and summarize workflow results
Some jobs failed. Failing workflow.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
workflow
|
95.7 KB |
sha256:e4458e17de706c6f621dc13f98666edafcd383e28def32bb2fb355d63fe8359e
|
|
|
zz_jobs-C8
|
5.09 KB |
sha256:6ef9a05aa4141ec675551f9a52543f7f72c57a93ad24649b1bb96f5656bd62cf
|
|
|
zz_jobs-DA
|
5.14 KB |
sha256:5b49a02f1e0f97744c45ab9f181b03ae32b85a9651769eaade5da09190e9417a
|
|
|
zz_jobs-DE
|
5.14 KB |
sha256:4536fdd0cf84a2ab6c792d40b64f1d6fc2929271659bb9eadbf909a766d7244e
|
|
|
zz_jobs-DI
|
5.15 KB |
sha256:aff51f0951c6774dfa26499c93a928dae103ddff191ae3e3afa32c347104570c
|
|
|
zz_jobs-E
|
15.1 KB |
sha256:d244f2370d9fe311fc4ce4d39371b1162398bb83921d269cf4e77d7d837448a5
|
|
|
zz_jobs-I
|
15.4 KB |
sha256:36785184379aab9ba6fc47a45de8c3d320c08cf28d2104a1f24d198647b57222
|
|
|
zz_jobs-M
|
7.67 KB |
sha256:f61632361762822d5c12797ab3787e925e0d971101a8370976d38b6401fa6f69
|
|
|
zz_jobs-Q
|
4.88 KB |
sha256:ee39f6a62d0929f36a793daab8d3cd0b125395417d77976e7245c0558ca6e37f
|
|
|
zz_jobs-U
|
7.64 KB |
sha256:7aca65643735a34b018a999718a2588ddd1b2b90f2f589f9c8e51eddd4a2b61e
|
|
|
zz_jobs-Y
|
7.62 KB |
sha256:ade4b88a146ec59459f4691c5b6f232daca3bf5a618a3b42e7127033a2dbceb4
|
|