remove legacy tranformer and modules - #4207
Conversation
Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
|
/ok to test 53b28f3 |
Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
|
/ok to test 9dc4c7b |
There was a problem hiding this comment.
all of the model files (gpt_model.py, bert_model.py, t5_model.py, etc.) still point to this file. have these been removed in other PRs, or do they need to be removed in this PR?
There was a problem hiding this comment.
removing LayerNorm and RMSNorm also breaks existing model files. We need to either remove the models, or merge in main if they've already been removed.
There was a problem hiding this comment.
a few things that still depend on this module:
- megatron/training/checkpointing.py
- tools/checkpoint/loader_legacy.py
- examples/academic_paper_scripts/detxoify_lm/generate_samples_gpt.py
- examples/academic_paper_scripts/detxoify_lm/finetune_gpt.py
- examples/gpt3/gpt_config.yaml
Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
|
/ok to test 56ba238 |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/25408874973 |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/25410186567 |
|
/ok to test 0d4fc55 |
Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
|
/ok to test a1a6b5d |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/25494423909 |
…ync-2026-05 Upstream tip: 932d9ee (Add periodic GPU sniff tests, 2026-05-07). Conflict resolution: - 13 modify/delete conflicts in .github/* and skills/*: kept deletion (matches policy from c037427 removing upstream-NVIDIA CI machinery not relevant to this fork). - AGENTS.md content conflict: kept fork version (skills/contributing sections from upstream don't apply since the directories were removed). - New upstream additions matching the same removal policy were dropped: .claude/settings.json, .github/workflows/nightly-sync-main-to-dev.yml, skills/{cicd,linting-and-formatting,nightly-sync,run-on-slurm,testing, update-golden-values}/SKILL.md. - SECURITY.md (new from upstream): kept (generic security policy). Verified post-merge: - pretrain_gpt.py logging-patch hook intact (lines 405-408). - megatron/core/optimizer/__init__.py emerging_optimizers + muon logic intact. - megatron/training/arguments.py custom muon flags intact (lines 2297-2309). Notable upstream changes pulled in: - Removed legacy transformer + legacy GPT modules (NVIDIA#4207, NVIDIA#4322). - Docker base image bump to 26.04-py3 (NVIDIA#4611). - Inference fixes (vLLM grouped GEMM NVIDIA#4566, FlashInfer sampling NVIDIA#2456, EP sync NVIDIA#4607, MoE dispatcher fixes NVIDIA#4576). - Gradient corruption fix with layerwise param all-gather overlap (NVIDIA#4609). - Hybrid model + Flextron + GPU sniff tests + named validation sets + fault injection + InJob restart.
Signed-off-by: dimapihtar <dpykhtar@nvidia.com> Signed-off-by: yhgalaxy <yhgalaxy@outlook.com>
Signed-off-by: dimapihtar <dpykhtar@nvidia.com> Signed-off-by: Jon Barker <jbarker@aws-cmh-slurm-1-vscode-02.cm.cluster>
Signed-off-by: dimapihtar <dpykhtar@nvidia.com>
Signed-off-by: dimapihtar <dpykhtar@nvidia.com> Signed-off-by: Dmytro Pykhtar <dpykhtar@nvidia.com>
What does this PR do ?
Removes legacy tranformer and other legacy modules as a part of MLM code cleanup.
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.