Skip to content

[CICD] Upload unittest coverage report to FlagCICD platform & Use BAAI runner#28

Merged
Darryl233 merged 23 commits into
flagos-ai:mainfrom
BrianPei:pr-0402
Apr 13, 2026
Merged

[CICD] Upload unittest coverage report to FlagCICD platform & Use BAAI runner#28
Darryl233 merged 23 commits into
flagos-ai:mainfrom
BrianPei:pr-0402

Conversation

@BrianPei

@BrianPei BrianPei commented Apr 3, 2026

Copy link
Copy Markdown
Collaborator

Description

Adds coverage report collection and upload functionality to the common unit test workflow (unit_tests_common.yml), and updates the MetaX runner label to match the new CI node.

Type of change

  • New feature (non-breaking change which adds functionality)
  • Infra/Build change (changes to CI/CD workflows or build scripts)
  • Code refactoring
  • Documentation change
  • Bug fix
  • Breaking change

Changes

  • Inlined coverage logic into the Run unit tests step: wraps the torchrun invocation with coverage run --parallel, then runs coverage combine + coverage json after tests complete, outputting results to coverage-report/
  • Added Upload Coverage Report step to save the JSON report as a CI artifact via actions/upload-artifact@v4
  • Added Upload Coverage Report to FlagCICD step that calls flagos-ai/FlagOps/actions/post-pytest-report@v2 to push coverage data to the FlagCICD platform
  • Updated runner label in .github/configs/metax.yml to mx-4g-cicd-test

Checklist:

  • I have read and followed the contributing guidelines
  • The functionality is complete
  • I have commented my code, particularly in coverage report uploading steps
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added/updated tests that prove my feature works on Cuda and Metax platform
  • New and existing unit tests pass locally on Cuda and Metax platform

Copilot AI review requested due to automatic review settings April 3, 2026 10:16

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR enhances the shared unit test reusable workflow by generating a Python coverage JSON report per test-group run and uploading it both as a GitHub Actions artifact and to the FlagCICD platform. It also updates the Metax runner label to target the new CI node.

Changes:

  • Added a upload_coverage workflow input (default true) to control coverage generation/upload.
  • Wrapped the torchrun pytest execution with coverage collection and post-processing to a JSON report in coverage-report/.
  • Uploaded the coverage report as an artifact and posted it to FlagCICD; updated Metax runner label to mx-4g-cicd-test.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/unit_tests_common.yml Adds coverage generation, artifact upload, and FlagCICD upload steps to the common unit test workflow.
.github/configs/metax.yml Updates Metax runner label configuration to use the new runner label.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/unit_tests_common.yml Outdated
Comment thread .github/workflows/unit_tests_common.yml

@Darryl233 Darryl233 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lxd-cumt lxd-cumt left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Darryl233 Darryl233 changed the title [wip] [CICD] Upload unittest coverage report to FlagCICD platform & Use BAAI runner [CICD] Upload unittest coverage report to FlagCICD platform & Use BAAI runner Apr 13, 2026
@Darryl233 Darryl233 merged commit de0f473 into flagos-ai:main Apr 13, 2026
77 of 101 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants