ci: introduce L-tier scope vocabulary via parser - #4625
Merged
Conversation
Add LEGACY_SCOPE_ALIASES in recipe_parser.py that maps legacy scope values
(mr, mr-slim, mr-github, mr-github-slim, nightly, weekly) to the new L-tier
vocabulary (L0/L1/L2/L3). The alias rewrites `scope` per workload row in
flatten_products and injects a default cadence only when the legacy name
implied a trigger (nightly -> [nightly], weekly -> [weekly]) and the
recipe has no explicit cadence set. Add `weekly` to ALLOWED_CADENCE_VALUES.
Flip in-repo CI call sites to the new tier names so new contributors only
see L0/L1: cicd-main.yml configure step picks L0/L1 instead of
mr-github-slim/mr-github; dev defaults in launch_jet_workload.py and
generate_local_jobs.py default to L1; tools/bisect.{sh,md} reference L1.
unit-tests is intentionally not aliased - .gitlab/stages/02.test.yml
still passes that exact string and the recipes still declare it. The
GitLab FUNCTIONAL_TEST_SCOPE variable is set externally and continues
to send legacy values; the alias resolves them transparently. A comment
in 04.functional-tests.yml documents this.
Recipe YAMLs are not edited; they continue to work via the alias.
Contributor
Author
|
/ok to test 10cad0d |
@balasaajay, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/2/ |
Contributor
Author
|
/ok to test f596ee9 |
Change the default scope from 'L1' to 'mr' in generate_local_jobs.py and launch_jet_workload.py to align with the legacy values used in GitLab CI. Update documentation in bisect.md to reflect this change. Adjust comments in recipe_parser.py to clarify the handling of legacy scope values and their mapping to the new L-tier vocabulary.
Contributor
Author
|
/ok to test b168601 |
ko3n1g
approved these changes
May 6, 2026
Contributor
Author
|
/ok to test 7684cf6 |
Contributor
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/25460146025 |
5 tasks
balasaajay
added a commit
to balasaajay/Megatron-LM
that referenced
this pull request
May 20, 2026
yhgalaxy
pushed a commit
to yhgalaxy/Megatron-LM
that referenced
this pull request
Jun 17, 2026
Signed-off-by: yhgalaxy <yhgalaxy@outlook.com>
jon-barker
pushed a commit
to jon-barker/Megatron-LM
that referenced
this pull request
Jul 10, 2026
Signed-off-by: Jon Barker <jbarker@aws-cmh-slurm-1-vscode-02.cm.cluster>
terminator123
pushed a commit
to 021ai/Megatron-LM
that referenced
this pull request
Aug 3, 2026
terminator123
pushed a commit
to 021ai/Megatron-LM
that referenced
this pull request
Aug 3, 2026
svcnvidia-nemo-ci
pushed a commit
to dimapihtar/Megatron-LM
that referenced
this pull request
Aug 4, 2026
Signed-off-by: Dmytro Pykhtar <dpykhtar@nvidia.com>
svcnvidia-nemo-ci
pushed a commit
to dimapihtar/Megatron-LM
that referenced
this pull request
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do ?
Add LEGACY_SCOPE_ALIASES in recipe_parser.py that maps legacy scope values (mr-github, mr-github-slim, nightly, weekly) to the new L-tier vocabulary (L0/L1/L2/L3). The alias rewrites scope per workload row in flatten_products and injects a default cadence only when the legacy name implied a trigger (nightly -> [nightly], weekly -> [weekly]) and the recipe has no explicit cadence set. Add weekly to ALLOWED_CADENCE_VALUES.
Follow up PR:
Rewrite recipe scope: values to L-tier names as recipes are touched.
[mr]/[mr-github] → [L1],
[*-slim] → [L0],
[nightly] → [L2] + cadence: [nightly],
[weekly] → [L3] + cadence: [weekly].
unit-tests and *-broken stay as-is.
Issue tracking
For PRs from open-source community contributors:
Linked issue:
Contribution process
Pre-checks
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"
.github/CODEOWNERS.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, theFinal Reviewlabel 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
Approvedlabel 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.comorzijiey@nvidia.com.