cuda_tests #104
all_tests_cuda.yml
on: workflow_dispatch
run_tests
/
checkout_and_config
5s
Matrix: run_tests / unit_tests
Matrix: run_tests / integration_tests
Waiting for pending jobs
all_tests
3s
Annotations
23 errors and 5 warnings
|
run_tests / unit_tests (a100) / unit-a100-pytorch_debug
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 129342 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_debug
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130928 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
The process '/usr/bin/git' failed with exit code 128
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 129343 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 129436 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130518 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
The process '/usr/bin/git' failed with exit code 128
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 131392 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130437 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130536 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
The process '/usr/bin/git' failed with exit code 128
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130349 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 129242 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130006 ms: Connection timed out
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_unittest
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.
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch-unittest-coverage
unable to access 'https://github.com/BrianPei/TransformerEngine-FL/': Failed to connect to github.com port 443 after 130114 ms: Connection timed out
|
|
run_tests / unit_tests_complete
Process completed with exit code 1.
|
|
run_tests / integration_tests_complete
Process completed with exit code 1.
|
|
run_tests / all_tests_complete
Process completed with exit code 1.
|
|
all_tests
Process completed with exit code 1.
|
|
cuda_tests
The run was canceled by @qqjxzxq.
|
|
cuda_tests
The run was canceled by @qqjxzxq.
|
|
cuda_tests
The run was canceled by @qqjxzxq.
|
|
run_tests / checkout_and_config
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 16th, 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/
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_distributed_unittest
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_debug
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch_onnx_unittest
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 16th, 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/
|
|
run_tests / unit_tests (a100) / unit-a100-pytorch-unittest-coverage
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 | |
|---|---|---|---|
|
coverage-cuda-a100-pytorch-unittest
|
160 KB |
sha256:5a6d04b00a0049e0c44728f6764caac917abb0a75d66ff16483796ac3e98c249
|
|
|
coverage-cuda-a100-pytorch_debug
|
185 KB |
sha256:1f6f72fab744ce822e7ca85483bfc775cb80fca457f1ea041c3535d080e88127
|
|
|
coverage-cuda-a100-pytorch_distributed_unittest
|
179 KB |
sha256:7ef1c60958c4c270302e505b1edeeac1c6b4e075e89f0f0221d9da4f02f46880
|
|