Skip to content

CICD NeMo

CICD NeMo #10960

Manually triggered April 11, 2026 20:04
Status Success
Total duration 18m 23s
Artifacts 2

cicd-main.yml

on: workflow_dispatch
pre-flight  /  pre-flight
10s
pre-flight / pre-flight
configure
5s
configure
Lint check
18s
Lint check
cicd-wait-in-queue
3s
cicd-wait-in-queue
cicd-container-build
3m 55s
cicd-container-build
Launch_Unit_Tests_Core
4m 20s
Launch_Unit_Tests_Core
Launch_Unit_Tests_Diffusion
2m 15s
Launch_Unit_Tests_Diffusion
generate-test-matrix
7s
generate-test-matrix
Matrix: cicd-functional-tests-l1
Matrix: cicd-functional-tests-l2
Matrix: cicd-functional-tests-l0
Matrix: cicd-functional-tests-flaky
Nemo_CICD_Test
5s
Nemo_CICD_Test
Coverage_Fake
0s
Coverage_Fake
Matrix: Coverage
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
svcnvidia-nemo-ci
approved Apr 11, 2026
test

Automatically approved by queue manager

Annotations

1 error and 6 warnings
cicd-container-build
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
pre-flight / pre-flight
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, step-security/[email protected]. 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/
pre-flight / pre-flight
Please ensure that submodules are initialized and up to date. See: https://github.com/actions/checkout#usage
pre-flight / pre-flight
fatal: Invalid revision range d30c3ae5469fe3f6a64d4fd2e63b6e7f7844ea81..59fc89485f18c47038c0cb9aed65a35850030d34
pre-flight / pre-flight
Set 'fetch_additional_submodule_history: true' to fetch additional submodule history for: 3rdparty/Megatron-LM
pre-flight / pre-flight
Unable to find merge base between d30c3ae5469fe3f6a64d4fd2e63b6e7f7844ea81 and 59fc89485f18c47038c0cb9aed65a35850030d34
cicd-container-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, 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
coverage-unit-test-24290512526-72a46fae-6794-4c59-a9fb-77e6c3f7a2eb
260 KB
sha256:d993bc5b8ee9e9dcf322b0825683a84cd9c84c216a2260968f8d1d34ffd5181f
coverage-unit-test-24290512526-96fde43d-14b9-474c-b322-432ea0079466
297 KB
sha256:3d6947c1ad2361bc9c279f75199f9facf4236360da64c3bed69bbe44d471cdb2