add is_torch_min_version in fsdp src - #4812
Conversation
Signed-off-by: Xiaowei Ren <xren@nvidia.com>
|
This PR has been automatically converted to draft because all PRs must start as drafts. When you are ready for review, click Ready for Review to begin the review process. This will:
See the contribution guide for more details. |
|
/ok to test f9b1a20 |
cspades
left a comment
There was a problem hiding this comment.
LGTM, I made a similar change in my CG PR where I will remove the MCore import from DDPConfig but I like this better, just have a util for it.
| import torch | ||
|
|
||
| from megatron.core.utils import is_torch_min_version | ||
| from .utils import is_torch_min_version |
There was a problem hiding this comment.
can we use a full path?
There was a problem hiding this comment.
There's two possible paths depending on the install:
megatron.core.distributed.fsdp.src.megatron_fsdp.utils
megatron_fsdp.utils
| _torch_version = PkgVersion(torch.__version__) | ||
| except Exception: | ||
| # This is a WAR for building docs, where torch is not actually imported | ||
| _torch_version = PkgVersion("0.0.0") |
There was a problem hiding this comment.
Will this lead to weird error messages where it says torch is too old when in fact it isn't even installed?
|
/ok to test 0238c1b |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/25983840395 |
* origin/main: (138 commits) Refactor CUDA graph API: decompose cuda_graph_scope into full_iteration impl, inference scope, and per-layer capture modules (NVIDIA#4292) Add high-priority A2A stream and HybridEP preprocessing SMs (NVIDIA#4694) add is_torch_min_version in fsdp src (NVIDIA#4812) [Main][feat] Support A2A Overlap for Megatron-FSDP (NVIDIA#3797) Reorder mtp_post_process after attention backward in 1F1B schedule plan (NVIDIA#4695) [fix] Use MSC for checking checkpoint existence (NVIDIA#4251) Combine GEMM + SwiGLU fused MLP PRs (3890, 4071, 4095, 4219, 4311, 4324) → main (NVIDIA#4636) Strengthen test_checkpoint to verify distributed checkpoint behavior (NVIDIA#4711) Disable MSC by default; opt in via --enable-msc (NVIDIA#4629) additional tests for nvrx (NVIDIA#4522) Update copy-pr-bot.yaml [skip ci] ci: tolerate git-gc race in /home/runner chown after checkout (NVIDIA#4808) Inference: Optimize Prefill Engine Steps for Nemotron (NVIDIA#4764) chore: Update nightly tests golden values (NVIDIA#4805) ci: Update workflow to use same commit for building docker image and running tests (NVIDIA#4787) Update owners (NVIDIA#4794) Bump nvidia-modelopt>=0.44.0 (NVIDIA#4803) fix tokenizers in respect to newer transformers (NVIDIA#4608) Use Protocols to type-check linear_proj submodules of Attention (NVIDIA#3434) Fix recompute checkpointing + training CGs (NVIDIA#3919) ... # Conflicts: # megatron/core/transformer/moe/moe_utils.py
Signed-off-by: Xiaowei Ren <xren@nvidia.com> Co-authored-by: Philip Petrakian <ppetrakian@nvidia.com>
Signed-off-by: Xiaowei Ren <xren@nvidia.com> Co-authored-by: Philip Petrakian <ppetrakian@nvidia.com> Signed-off-by: yhgalaxy <yhgalaxy@outlook.com>
Signed-off-by: Xiaowei Ren <xren@nvidia.com> Co-authored-by: Philip Petrakian <ppetrakian@nvidia.com> Signed-off-by: Jon Barker <jbarker@aws-cmh-slurm-1-vscode-02.cm.cluster>
Signed-off-by: Xiaowei Ren <xren@nvidia.com> Co-authored-by: Philip Petrakian <ppetrakian@nvidia.com>
Signed-off-by: Xiaowei Ren <xren@nvidia.com> Co-authored-by: Philip Petrakian <ppetrakian@nvidia.com> Signed-off-by: Dmytro Pykhtar <dpykhtar@nvidia.com>
What does this PR do ?
To fix this FSDP wheel building issue.
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.