Test RAPIDS build times #28
trxcllnttest-rapids-build-times.yml
on: workflow_dispatch
Check GH Event
2s
Matrix: test-rapids-build-times
Annotations
1 error and 15 warnings
|
build cluster: no / arm64, 12.9, conda
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: yes / 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 cluster: no / 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 cluster: no / 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 cluster: no / 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 cluster: no / 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 cluster: no / 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 cluster: no / 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 cluster: no / 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
sccache-client-logs-cuda12.9-conda-amd64-23970960044-1-26397
|
590 KB |
sha256:b9d3b3bfbe2f57e8652236613de5cc6cfc2292865dcb7ecf66ced1e4bbc68009
|
|
|
sccache-client-logs-cuda12.9-conda-amd64-23970960044-1-30417
|
593 KB |
sha256:bb2dff809e4350873af6f4b4485279e594ff5dc724d5abff5d834d509ec73d55
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23970960044-1-30859
|
590 KB |
sha256:947d109f067fa58b00489620251fb25eed94599501f9b54b9b52bbe50416b412
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23970960044-1-16901
|
620 KB |
sha256:f793267288750a3cf6d6ac646c95fad0591a406cd9c27c02d8120735a9d4fd10
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23970960044-1-28242
|
620 KB |
sha256:bc2181c1a1b0d00a51f4f26951fd50b6f6db70f9ac73a9f103cbca7f462b266c
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23970960044-1-24099
|
619 KB |
sha256:9675602f43f9a262feb65b94e07cc2f5b4dc9e01306f017caac8a64c01e09446
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23970960044-1-688
|
2.39 MB |
sha256:3ff16e71de139c0902f6b5ffd7fec26e012cb8957fb4a2bdf947dc9110005c5e
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23970960044-1-15499
|
677 KB |
sha256:79c0497a5400f9977c36e22dbb99408bdaf7589293cede585a76f8bed4c39cc5
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23970960044-1-9238
|
676 KB |
sha256:84ec9c9e246f95b7f2e9653177cb848d8b607191ea5c3cf7e3487234a86d1ad6
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23970960044-1-1013
|
674 KB |
sha256:28a2b1cf325e7cd79ab7fddff2a45ac0ba9175ab75e11a2975b78c86b2eb223a
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23970960044-1-8561
|
671 KB |
sha256:dd58f1da6aaa6f09974a984aeb670de188e1aaa087597d7a748360a81919df6b
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23970960044-1-12503
|
703 KB |
sha256:821603d09c69393e5c0ed028ea65ef9170da07b8099378d65e2c9867035c98cc
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23970960044-1-14979
|
701 KB |
sha256:e86295d574c81443160f40295c74bf9259264c9d6b6971c4f60d908d18d185ff
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23970960044-1-20140
|
701 KB |
sha256:e73f92f09786ce174df5960b8bd7f1f9245b04a6a913e8846d2b8dbae9aa50ea
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23970960044-1-7946
|
2.44 MB |
sha256:1d00b45b235c9284be32444b073c62319e12e4c5769b2ac9c38109bab3dd6298
|
|