Skip to content

[DO NOT MERGE] MLPERF HOTFIX: Default gradient communication dtype to BF16.#3807

Draft
cspades wants to merge 1 commit intoNVIDIA:mainfrom
cspades:cye/patch-grad-comm-wgrad-fuse
Draft

[DO NOT MERGE] MLPERF HOTFIX: Default gradient communication dtype to BF16.#3807
cspades wants to merge 1 commit intoNVIDIA:mainfrom
cspades:cye/patch-grad-comm-wgrad-fuse

Conversation

@cspades
Copy link
Member

@cspades cspades commented Mar 11, 2026

What does this PR do ?

  • DO NOT MERGE THIS IS A HOTFIX

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

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.

@cspades cspades self-assigned this Mar 11, 2026
@copy-pr-bot
Copy link

copy-pr-bot bot commented Mar 11, 2026

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@cspades cspades force-pushed the cye/patch-grad-comm-wgrad-fuse branch from 8009e93 to 111d1c2 Compare March 11, 2026 17:37
Signed-off-by: Cory Ye <cye@nvidia.com>
@cspades cspades force-pushed the cye/patch-grad-comm-wgrad-fuse branch from 111d1c2 to e073fb4 Compare March 11, 2026 18:12
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