install libprotobuf-dev and protobuf-compiler-grpc #3822
copy-pr-bot[bot]test.yml
on: push
Check PR Event
4s
Matrix: Build / build-all-rapids-repos
Matrix: Feature integration / test
Matrix: run-feature-scenario-tests
Matrix: run-generated-feature-tests
Matrix: build-and-test-linux-images
Matrix: build-and-test-windows-images
Waiting for pending jobs
Annotations
12 errors and 37 warnings
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 13.1, pip
Build C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 12.9, pip
Build C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 13.1, pip
Build C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
Build / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 12.9, pip
Build C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
Validate Features
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/setup-node@v4, devcontainers/action@v1. 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/
|
|
Determine features matrix
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/github-script@v7, step-security/changed-files@3dbe17c78367e7d60f00d78ae6781a35be47b4a1. 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/
|
|
Determine image matrix
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/github-script@v7, step-security/changed-files@3dbe17c78367e7d60f00d78ae6781a35be47b4a1. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / amd64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / amd64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / arm64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / amd64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / amd64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / arm64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / arm64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / arm64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 nvhpc feature / 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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / arm64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / arm64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx kvikio dask-cuda cudf cudf_kafka rapidsmpf / amd64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 nvhpc feature / amd64
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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / amd64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / arm64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / amd64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 13.1, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 12.9, conda
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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/
|
|
nvhpc26.3-ubuntu:24.04 / amd64
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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
|
|
nvhpc26.1-ubuntu:24.04 / amd64
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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / arm64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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/
|
|
nvhpc26.3-ubuntu:24.04 / 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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
|
|
nvhpc26.1-ubuntu:24.04 / 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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / arm64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 13.1, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 / rmm ucxx dask-cuda raft cuvs cuml nvforest cuopt / amd64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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/
|
|
Feature integration / 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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
|
|
Feature integration / amd64
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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 nvhpc scenarios / 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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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 / rmm ucxx dask-cuda raft cugraph cugraph-gnn nx-cugraph / amd64, 12.9, pip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6. 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 nvhpc scenarios / amd64
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/setup-node@v4, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
sccache-client-logs-cuda12.9-conda-amd64-23826996630-1-13057
|
362 KB |
sha256:21767068870aff186246bb5fb9cc7b37fb425b06ac6fe7b738ec0ada7fdedd75
|
|
|
sccache-client-logs-cuda12.9-conda-amd64-23826996630-1-25570
|
370 KB |
sha256:1eb3c795c745e5d22ab47efd037902d955ca27cf338c62cf7fb004f59fc444c8
|
|
|
sccache-client-logs-cuda12.9-conda-amd64-23826996630-1-30814
|
207 KB |
sha256:02cdbb6e145eeeee76548c1d4d2d841fd652a95b3e32ce2a8d8f4a9846374e0d
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23826996630-1-16268
|
357 KB |
sha256:3bf0dd90ccd96645e485c045ea58e88e27b93f4ebc83cbd7f6e388d87b09e03b
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23826996630-1-18371
|
205 KB |
sha256:152caf5072e72116c422d57c154c7846701ba813d17891a44e05485cc58154c1
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23826996630-1-6954
|
369 KB |
sha256:8797f61b157cd357190ec9e10218cbb668e3ddde56a5fdf4e6fe5cb731d59b0e
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23826996630-1-2208
|
592 KB |
sha256:edfcbbf194a4b57f8b24f18a01c7dda625f875db5689c254f918667621daf6b0
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23826996630-1-6650
|
398 KB |
sha256:635c7661ceac271a671a4038dbf0fcb4d10b3ac7c70d4628ec795d781a4efa6d
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23826996630-1-7081
|
1.26 MB |
sha256:f1eb4727f61763a772fda31390b6879968cd509f0e0de4a1d816eba8b6b00cda
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23826996630-1-18284
|
518 KB |
sha256:2a612f5c4a4d890d4f52493b211e02b86e792b1fb174f8ea287ea1e4566846be
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23826996630-1-24708
|
400 KB |
sha256:ea8423c9cd9d2fc42a5d62ea796ff8f9a094f038b80f787ea824cd925ab6113f
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23826996630-1-9185
|
583 KB |
sha256:15b319e96e5eefade80b8fe4fe6ee673dd867ea65cdfa9a55bd1e4348ce14fff
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23826996630-1-14820
|
361 KB |
sha256:b9d5dce477a180ee4539bd1331c85a9b190d7c72041dcc6244c19eaac1815ae2
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23826996630-1-29236
|
207 KB |
sha256:989f59808fca1155243b55b19ca21743c38f52981dcf404a314fd87655732a43
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23826996630-1-764
|
372 KB |
sha256:6588654d3bd7e8f6c6d1eda7d7170261649d860455526520f02cf1c97ee7de8e
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23826996630-1-1017
|
370 KB |
sha256:5fd4309c8b45583621a384651c7ddc70bee527e2c01251b173cb805b6a15c52b
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23826996630-1-29681
|
206 KB |
sha256:7ab4dadb944a868db3da5dd48afe3a17e96d9c08ce32719aa64b957d5da5b6e2
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23826996630-1-7544
|
362 KB |
sha256:2356a9560a74912fe0075fc2f8113b49815924fccaf149eb3df1a2f0b84ae328
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23826996630-1-12234
|
523 KB |
sha256:3174623915d2213ca11f19135bc9816c420327d0951ed840201b50beddfb014b
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23826996630-1-23587
|
569 KB |
sha256:ef4e241f083deaee2f452dccefebbd3b14da2725ca66fe30fad5439d4dbc6e7b
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23826996630-1-5337
|
403 KB |
sha256:7f26256f38c272931595a96a14fc54f4274fed12fcc6e59871085d905266ee06
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23826996630-1-10402
|
562 KB |
sha256:5abc7f49cd7307663bdab1c59056dbb73af98cef5447f7403e0130ed15f631f0
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23826996630-1-14466
|
523 KB |
sha256:2f9ecb0c7cbb72ffc239b37597792fec9fa8e428155fcd8c5e925847d4c58ff4
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23826996630-1-15622
|
394 KB |
sha256:150505f4fe12a12912b29fb7560940906447656b1bec1506f1dad29c904dd255
|
|