Skip to content

move nvforest before cuml and bump feature version #3969

move nvforest before cuml and bump feature version

move nvforest before cuml and bump feature version #3969

Triggered via push May 22, 2026 17:22
Status Success
Total duration 49m 59s
Artifacts 24

test.yml

on: push
Check PR Event
2s
Check PR Event
pre-commit
10s
pre-commit
Build  /  Check GH Event
4s
Build / Check GH Event
Validate Features
20s
Validate Features
Matrix: Build / build-all-rapids-repos
Determine features matrix
9s
Determine features matrix
Determine image matrix
11s
Determine image matrix
Matrix: Feature integration / test
Matrix: run-feature-scenario-tests
Waiting for pending jobs
Matrix: run-generated-feature-tests
Matrix: build-and-test-linux-images
Waiting for pending jobs
Matrix: build-and-test-windows-images
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/
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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, devcontainers/action@1082abd5d2bf3a11abccba70eef98df068277772. 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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b, 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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b, 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/
Test rapids-build-utils 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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test rapids-build-utils 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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
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@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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
sccache-client-logs-cuda12.9-conda-amd64-26302103957-1-21887
436 KB
sha256:b8aab4a48065c6af12cff7c3f903785614bce7d567b0ea5f065c38e2b1887a70
sccache-client-logs-cuda12.9-conda-amd64-26302103957-1-4575
273 KB
sha256:2d166f48febed5511dba6ea5b6d3aa3a48032bef37a81078d13e4317f7680e67
sccache-client-logs-cuda12.9-conda-amd64-26302103957-1-6699
1.03 MB
sha256:593174037b71b6b20bde6a4339ba4faae22cbedbb81b4fc357a5638aab773a27
sccache-client-logs-cuda12.9-conda-arm64-26302103957-1-12026
1 MB
sha256:3fc6f1adeca157352c4ee8e4a8843a228b3101380dd3bcfcc43d204d19fc25d5
sccache-client-logs-cuda12.9-conda-arm64-26302103957-1-18583
429 KB
sha256:71d811d7ca5443a93fd66c9c3f508032208159f620801cb9fabef0af671d451b
sccache-client-logs-cuda12.9-conda-arm64-26302103957-1-900
268 KB
sha256:932f1abbfe6a24c8c407b8a7273bd918d4a24ae8fb1f9c5e596623453a50d565
sccache-client-logs-cuda12.9-pip-amd64-26302103957-1-22592
472 KB
sha256:fc62cb0135bc13a4575c58aaf55842fd08e7d1bd807ffce9bf0c053e18f3b8fc
sccache-client-logs-cuda12.9-pip-amd64-26302103957-1-25122
909 KB
sha256:a0928115308b2771704b66c0e0e1a0c79372907764f3eda5bd4d891512ee3f0c
sccache-client-logs-cuda12.9-pip-amd64-26302103957-1-8424
1.04 MB
sha256:99e61058f64a357e6d20c73efeb9380cda6274ef6e0132d3355b88925da3f87e
sccache-client-logs-cuda12.9-pip-arm64-26302103957-1-10860
919 KB
sha256:330a2fe9ecd478a27929c26325cde188e1c80fbc6204032cdcd8c851da19507d
sccache-client-logs-cuda12.9-pip-arm64-26302103957-1-21273
1.03 MB
sha256:e7dbe9a7e9037cbcee714c4428c56188b48e41f49ef2e0c081616b034beeeae2
sccache-client-logs-cuda12.9-pip-arm64-26302103957-1-21416
470 KB
sha256:d4a3aef5498c602d3398f45e05f471067fd92b6bbf7fb451f1f78272fe8d0828
sccache-client-logs-cuda13.2-conda-amd64-26302103957-1-32589
436 KB
sha256:b4a69900aa59d65b2d8337f05161c02bdb4bf096c11b236c462a540805b93b46
sccache-client-logs-cuda13.2-conda-amd64-26302103957-1-3535
271 KB
sha256:6b13d86827f7d4663d753a0df92dd1453a69f1914f7fcf3fe5360a75f25ddd09
sccache-client-logs-cuda13.2-conda-amd64-26302103957-1-5978
910 KB
sha256:51996f13aaf09953e58801f7fd53f232777da08b1b5d743c601864ee59391410
sccache-client-logs-cuda13.2-conda-arm64-26302103957-1-1074
991 KB
sha256:6dcea5c0a2197a90af5e4f90d80c0d768d89c516d0908745c23f6740cbee8c13
sccache-client-logs-cuda13.2-conda-arm64-26302103957-1-32328
431 KB
sha256:3f6b5f052d2ab2da20960125e5329519ca84816079f20ab3d45c7b996cfcb2e7
sccache-client-logs-cuda13.2-conda-arm64-26302103957-1-6508
273 KB
sha256:f849bb03b3430d6e7a9ededa4555441589ce6c3812926f419199c601f1b296f4
sccache-client-logs-cuda13.2-pip-amd64-26302103957-1-31816
900 KB
sha256:2ff27a1ed31bab687882c23dd8970eea9356e8f6f1b726fdfd2ebec69f8cea14
sccache-client-logs-cuda13.2-pip-amd64-26302103957-1-72
473 KB
sha256:122b2e2d08b0db678fab02dae18b31bb3436fb88b9392c77c2b07e521e479986
sccache-client-logs-cuda13.2-pip-amd64-26302103957-1-8711
1.01 MB
sha256:4513a3e7fa7c533765d11a4b54f250ad8900f17ed1c9631afe3708427daba9fb
sccache-client-logs-cuda13.2-pip-arm64-26302103957-1-24428
466 KB
sha256:8f8448d580e15ec3e6aeac2bb37ad3d36d4c2256eb55f829be4e2592535355ab
sccache-client-logs-cuda13.2-pip-arm64-26302103957-1-5157
1010 KB
sha256:e66cb1a61a1d0d3d2224287e7da02dec8de05d6457a2c8b419272abc50585daf
sccache-client-logs-cuda13.2-pip-arm64-26302103957-1-6862
915 KB
sha256:fb5446d7b203ef00c99a8615a0fcc09af801e356248f3533ac2fcc9ac2ea61dd