Skip to content

Fix for RL Test - #3148

Merged
wdykas merged 7 commits into
NVIDIA:mainfrom
wdykas:rl-testing
Feb 3, 2026
Merged

Fix for RL Test#3148
wdykas merged 7 commits into
NVIDIA:mainfrom
wdykas:rl-testing

Conversation

@wdykas

@wdykas wdykas commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

What does this PR do ?

Bringing back one of the RL tests with some changes to help make tests more deterministic.

⚠️ 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.

Contribution process

flowchart LR
    A[Pre-checks] --> B[PR Tests]
    subgraph Code Review/Approval
        C1[Expert Review] --> C2[Final Review]
    end
    B --> C1
    C2 --> D[Merge]
Loading

Pre-checks

  • I want this PR in a versioned release and have added the appropriate Milestone (e.g., Core 0.8)
  • 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

The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.

For MRs into `main` branch

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!

(Step 1): Add PR label Expert Review

(Step 2): Collect the expert reviewers reviews

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

(Step 3): Final Review

  1. Add Final Review label
  2. GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.

(Optional Step 4): Cherry-pick into release branch

If this PR also needs to be merged into core_r* release branches, after this PR has been merged, select Cherry-pick to open a new PR into the release branch.

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.

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@wdykas
wdykas requested review from a team as code owners January 29, 2026 18:22
@copy-pr-bot

copy-pr-bot Bot commented Jan 29, 2026

Copy link
Copy Markdown

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.

@ko3n1g
ko3n1g requested a review from a team January 29, 2026 18:22
@dimapihtar dimapihtar added Expert Review [deprecated] Apply this label to indicate that your PR is ready for expert review. complexity: medium labels Jan 29, 2026
@dimapihtar

Copy link
Copy Markdown
Contributor

/ok to test 8f77f6c

@jon-barker jon-barker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this is great - thanks!

@wdykas

wdykas commented Jan 30, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 27254b4

@ko3n1g ko3n1g left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

One comment regarding the model config

- "mem-allocated-bytes"
- "mem-max-allocated-bytes"

THROUGHPUT_TEST_PARAMS:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please don’t introduce new top-level attributes. If you need to feed metadata into your job, please use the pre-existing ENV mapping. It will export all of its key value pairs to the shell session

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@jon-barker I think I got this from you I think. Do you think we need this?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, the script that checks the metrics uses these to determine which metrics to compare and which iteration steps to use

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm happy for them to be moved into ENV_VARS @ko3n1g but I can't do it today and someone needs to check all the tests using this get updated. I can do it when i get back from vacation on 2/9

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ill do it in this MR and make sure the tests pass on gitlab before review

@wdykas

wdykas commented Feb 2, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 02a5bc3

@ko3n1g ko3n1g left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you!

@wdykas
wdykas enabled auto-merge February 2, 2026 18:27
@wdykas

wdykas commented Feb 2, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 02a5bc3

1 similar comment
@wdykas

wdykas commented Feb 3, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 02a5bc3

@wdykas
wdykas added this pull request to the merge queue Feb 3, 2026
Merged via the queue into NVIDIA:main with commit c4bea0a Feb 3, 2026
47 of 50 checks passed
@wdykas
wdykas deleted the rl-testing branch February 3, 2026 00:33
daiyaanarfeen pushed a commit to daiyaanarfeen/Megatron-LM that referenced this pull request Feb 23, 2026
Co-authored-by: Dmytro Pykhtar <37850217+dimapihtar@users.noreply.github.com>
yangbofun pushed a commit to xlm-research/Megatron-LM that referenced this pull request May 22, 2026
Co-authored-by: Dmytro Pykhtar <37850217+dimapihtar@users.noreply.github.com>
terminator123 pushed a commit to 021ai/Megatron-LM that referenced this pull request Aug 3, 2026
Co-authored-by: Dmytro Pykhtar <37850217+dimapihtar@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

complexity: medium Expert Review [deprecated] Apply this label to indicate that your PR is ready for expert review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants