Test RAPIDS build times #26
trxcllnttest-rapids-build-times.yml
on: workflow_dispatch
Check GH Event
3s
Matrix: test-rapids-build-times
Annotations
24 errors and 16 warnings
|
build cluster: no / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / amd64, 13.1, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: yes / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / amd64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / amd64, 13.1, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: yes / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / amd64, 12.9, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: no / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / amd64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / amd64, 12.9, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: no / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / arm64, 13.1, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: yes / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / arm64, 13.1, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / arm64, 13.1, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: yes / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: yes / arm64, 12.9, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
build cluster: no / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / arm64, 12.9, pip
Dev container exec failed: (exit code: 1)
|
|
build cluster: no / arm64, 12.9, pip
Configure C++ libraries - Failed (⬆️ click above for full log ⬆️)
|
|
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: 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: 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/
|
|
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: 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: 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: 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, 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, 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, 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 / 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
sccache-client-logs-cuda12.9-conda-amd64-23823427838-1-14414
Expired
|
617 KB |
sha256:adcb3e5b66da0323188cdbd593dd7f55696ad0bce564567aabd9919e05a4876f
|
|
|
sccache-client-logs-cuda12.9-conda-amd64-23823427838-1-24335
Expired
|
591 KB |
sha256:9f535c1c1a50f69366f8727d793bcf6f663d6475e70b192e52ec48f3a79307e2
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23823427838-1-15606
Expired
|
588 KB |
sha256:2b2d71524b5cd3782d2e1c5996da22aa221acbf407f9080842e2442f65f3a415
|
|
|
sccache-client-logs-cuda12.9-conda-arm64-23823427838-1-27602
Expired
|
620 KB |
sha256:600eaf8a82060baea5510edf6fee204691d743c6b0f17b214297e2d53f13ac4b
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23823427838-1-10206
Expired
|
50.3 KB |
sha256:709ba8b94021f581221e0bfa43c3201166dcca9030a888a8de8962cac08a645c
|
|
|
sccache-client-logs-cuda12.9-pip-amd64-23823427838-1-27094
Expired
|
50.3 KB |
sha256:a6e0db8c0bb126c8d421c5af1034ae83483ac4c3135305b43666f587a9b9a4b4
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23823427838-1-26627
Expired
|
50 KB |
sha256:98a6fceef16d97a444255dbee071a1d501e49bcf3aa6160de505003ac7d3f042
|
|
|
sccache-client-logs-cuda12.9-pip-arm64-23823427838-1-4050
Expired
|
50.1 KB |
sha256:5f22d351d8f5e4929eef7a82212f9a3401f93f0f204e1d3708e1d12cc636efd7
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23823427838-1-24075
Expired
|
714 KB |
sha256:b50197ca54fb3e57102b13f4bf7d23963cc6d5d02d0c1f718f78ada8045d6288
|
|
|
sccache-client-logs-cuda13.1-conda-amd64-23823427838-1-4392
Expired
|
740 KB |
sha256:b45d1333e8eb6a9230ba82c0b78dc6c3955f3daef8ed32fc962a218fb8d3a70f
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23823427838-1-19403
Expired
|
2.17 MB |
sha256:c7b31a2540617758c10c36c27797463829a8a8e7f36dfa467c737c30cbedd4df
|
|
|
sccache-client-logs-cuda13.1-conda-arm64-23823427838-1-27753
Expired
|
738 KB |
sha256:261d1d24e058853b0a4da88911405909609acc4edbc872d24006bd9a76bf9faa
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23823427838-1-31263
Expired
|
50.8 KB |
sha256:46a1befdfdb9960eded341d6ec89ffd6e1f9ec0faabbf9d235dee4c1f92062e7
|
|
|
sccache-client-logs-cuda13.1-pip-amd64-23823427838-1-7351
Expired
|
50.7 KB |
sha256:1b19d977d61b68f9a6643b5d036c64f46b972fa8ec6c16f3ae6352ef1abf1368
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23823427838-1-25502
Expired
|
50.6 KB |
sha256:38e864cbbc8b53674bf454dc2c4f408c2022fc5db62cffb9b9c46d9e1a90ffd6
|
|
|
sccache-client-logs-cuda13.1-pip-arm64-23823427838-1-3130
Expired
|
50.6 KB |
sha256:149858f68fbc380317c768c70ec0f93d01aa5cbd9ced0e24eb83f73dbb0acdac
|
|