Skip to content

ci: add cadence input for test filtering in CI workflows#4561

Draft
balasaajay wants to merge 7 commits intoNVIDIA:mainfrom
balasaajay:abalasa.main-tests-label
Draft

ci: add cadence input for test filtering in CI workflows#4561
balasaajay wants to merge 7 commits intoNVIDIA:mainfrom
balasaajay:abalasa.main-tests-label

Conversation

@balasaajay
Copy link
Copy Markdown
Contributor

@balasaajay balasaajay commented Apr 30, 2026

What does this PR do ?

  • Introduced a new cadence input in the GitHub Actions workflow to filter tests based on the trigger type (pr|nightly|mergegroup).
  • Updated the action YAML to include the cadence input and modified the test execution logic to respect this new parameter.
  • Enhanced documentation in SKILL.md to explain the cadence filter and its usage in test cases.
  • Updated relevant Python scripts to accept and process the cadence argument for test execution.

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

Issue tracking

For PRs from open-source community contributors:

  • New features: a linked issue is required. Please open a feature request and reference it here before submitting the PR.
  • Small updates (bug fixes, minor improvements): a linked issue is recommended and will accelerate the PR review process.

Linked issue:

Contribution process

Pre-checks

  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

- Introduced a new `cadence` input in the GitHub Actions workflow to filter tests based on the trigger type (pr|nightly|mergegroup).
- Updated the action YAML to include the `cadence` input and modified the test execution logic to respect this new parameter.
- Enhanced documentation in SKILL.md to explain the cadence filter and its usage in test cases.
- Updated relevant Python scripts to accept and process the `cadence` argument for test execution.
- Adjusted existing recipes to include cadence values for better test management.
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented Apr 30, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@balasaajay balasaajay changed the title feat: add cadence input for test filtering in CI workflows ci: add cadence input for test filtering in CI workflows Apr 30, 2026
@balasaajay
Copy link
Copy Markdown
Contributor Author

/ok to test bc8b163

@balasaajay
Copy link
Copy Markdown
Contributor Author

/ok to test ff867d8

@balasaajay
Copy link
Copy Markdown
Contributor Author

/ok to test 9ff6021

@balasaajay
Copy link
Copy Markdown
Contributor Author

/ok to test 015fda1

@balasaajay
Copy link
Copy Markdown
Contributor Author

balasaajay commented May 2, 2026

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.

1 participant