chore: Change submodule pointer for release#2191
Conversation
Signed-off-by: oliver könig <okoenig@nvidia.com>
📝 WalkthroughWalkthroughUpdated the git submodule pointer for 3rdparty/Megatron-LM to reference a newer commit, changing the pinned revision from bbbedbb9f53343762e4dc70abc771b813a83d817 to 76e81893449d69e54c3d43bdf6fca1accb9ce6e9. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Important Action Needed: IP Allowlist UpdateIf your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:
Failure to add the new IP will result in interrupted reviews. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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. |
…l, mock tokenizer - Remove explicit mtp_loss_scaling_factor=None from Qwen3NextModelProvider80B_A3B to inherit new mcore default of 0.1 - Mark Qwen3 MoE quantization tests as xfail: ModelOpt _QuantMoELayer does not support padding_mask yet - Add mock tokenizer with vocab_size, eod, and unique_identifiers to test_samplers for MockGPTLowLevelDataset compatibility
|
/ok to test 0bac8c0 |
MockGPTLowLevelDataset requires config.tokenizer.vocab_size and config.tokenizer.eod when building mock datasets. The three data loader tests were missing this, causing 'MockGPTDataset failed to build as a mock data generator' errors.
|
/ok to test 67d03f6 |
Signed-off-by: oliver könig <okoenig@nvidia.com>
|
/ok to test db91177 |
What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Changelog
GitHub Actions CI
See the CI sectionin the Contributing doc for how to trigger the CI. A Nvidia developer will need to approve and trigger the CI for external contributors.
Before your PR is "Ready for review"
Pre checks:
If you haven't finished some of the above items you can still open "Draft" PR.
Additional Information
Summary by CodeRabbit