Skip to content

[CICD] Expand unit test coverage on CUDA #58

[CICD] Expand unit test coverage on CUDA

[CICD] Expand unit test coverage on CUDA #58

Triggered via pull request May 28, 2026 05:07
Status Failure
Total duration 1h 0m 50s
Artifacts 3

build_image_cuda.yml

on: pull_request
Prepare build matrix
4s
Prepare build matrix
Matrix: build
Build summary
3s
Build summary
Load and push images
Load and push images
Run CUDA tests  /  checkout_and_config
Run CUDA tests / checkout_and_config
Run CUDA tests  /  ...  /  functional_test_cli
Run CUDA tests / cli_validation / functional_test_cli
Matrix: Run CUDA tests / unit_tests
Waiting for pending jobs
Matrix: Run CUDA tests / functional_tests_benchmark / functional_test_benchmark
Waiting for pending jobs
Matrix: Run CUDA tests / functional_tests_hetero_train / functional_test_hetero_train
Waiting for pending jobs
Matrix: Run CUDA tests / functional_tests_inference / functional_test_inference
Waiting for pending jobs
Matrix: Run CUDA tests / functional_tests_serve / functional_test_serve
Waiting for pending jobs
Matrix: Run CUDA tests / functional_tests_train / functional_test_train
Waiting for pending jobs
Run CUDA tests  /  all_tests_complete
Run CUDA tests / all_tests_complete
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 4 warnings
Build inference
buildx failed with: ERROR: failed to build: failed to solve: nvidia/cuda:12.8.1-devel-ubuntu22.04: failed to do request: Head "https://registry-1.docker.io/v2/nvidia/cuda/manifests/12.8.1-devel-ubuntu22.04": dial tcp 108.160.169.171:443: i/o timeout
Build train
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . /etc/profile.d/flagscale-env.sh && if [ \"$PKG_MGR\" = \"uv\" ]; then if [ ! -f \"${FLAGSCALE_HOME}/venv/bin/python3\" ]; then echo \"[ENV] Creating uv venv at ${FLAGSCALE_HOME}/venv (python=${PYTHON_VERSION})\"; \"$HOME/.local/bin/uv\" venv \"${FLAGSCALE_HOME}/venv\" --python \"${PYTHON_VERSION}\"; else echo \"[ENV] Found uv venv at ${FLAGSCALE_HOME}/venv\"; fi; elif [ \"$PKG_MGR\" = \"conda\" ]; then CONDA_ENV_NAME=flagscale-train; if [ -d \"${FLAGSCALE_CONDA}/envs/${CONDA_ENV_NAME}\" ]; then echo \"[ENV] Found conda env ${CONDA_ENV_NAME} at ${FLAGSCALE_CONDA}/envs/${CONDA_ENV_NAME}\"; else echo \"[ENV] Creating conda env ${CONDA_ENV_NAME} (python=${PYTHON_VERSION})\"; env CONDA_NO_PLUGINS=true ANACONDA_ACCEPT_TOS=yes \"${FLAGSCALE_CONDA}/bin/conda\" create -y -n \"${CONDA_ENV_NAME}\" \"python=${PYTHON_VERSION}\"; fi; else echo \"[ENV] Using system pip (no dedicated env to create)\"; fi" did not complete successfully: exit code: 127
Build all
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: nvidia/cuda:12.8.1-devel-ubuntu22.04: failed to do request: Head "https://registry-1.docker.io/v2/nvidia/cuda/manifests/12.8.1-devel-ubuntu22.04": dial tcp 108.160.169.178:443: i/o timeout
Build all
unable to access 'https://github.com/flagos-ai/FlagScale/': GnuTLS recv error (-110): The TLS connection was non-properly terminated.
Build summary
Process completed with exit code 1.
Build summary
One or more image builds failed
Prepare build 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 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 inference
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 train
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 all
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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
flagos-ai~FlagScale~5G7VZL.dockerbuild
11.8 KB
sha256:fedb9c3abf47ca637bea201c3994130d9f9177ae0f48658c143240586a0fd450
flagos-ai~FlagScale~RR4I35.dockerbuild
51.9 KB
sha256:bf473c9672948484589b27c605fa78e11a47cb8bfb6a29f4cecdd8cd1bc9ed01
flagos-ai~FlagScale~TCJ2JE.dockerbuild
11.9 KB
sha256:c6eadc741aae9a1f3f7d46baba412aa49544a6c3c8564f35e8aeb5ae4091cbe5