ci: add configurable launcher support for functional tests (ft_launcher / torchrun) - #4298
Merged
Merged
Conversation
|
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. |
Introduce a top-level `LAUNCHER` key in `model_config.yaml` (default: `torchrun`) that allows individual test cases to opt into `ft_launcher` (nvidia-resiliency-ext fault-tolerance launcher) as a drop-in torchrun replacement. All distributed arguments are forwarded unchanged; only the launcher binary is switched. Resolves AUT-360 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: oliver könig <okoenig@nvidia.com>
ko3n1g
force-pushed
the
ko3n1g/feat/ft-launcher-ci
branch
from
April 14, 2026 14:14
6c8d3cd to
e516859
Compare
Contributor
Author
|
/ok to test |
Enable ft_launcher (nvidia-resiliency-ext fault-tolerance launcher) for the following distributed optimizer / checkpoint-resume test cases: GPT: - gpt3_mcore_te_tp1_pp4_vp1_resume_torch_dist_dist_optimizer_overlap_grad_reduce_param_gather - gpt3_mcore_te_tp2_pp1_resume_torch_dist_multi_dist_optimizer_instances - gpt3_mcore_te_tp4_pp1_resume_torch_dist_dist_optimizer_overlap_grad_reduce_param_gather MoE: - gpt3_mcore_te_tp1_pp2_resume_torch_dist_reshard_2x1x4_te_8experts2parallel_dist_optimizer - gpt3_mcore_te_tp2_pp1_resume_torch_dist_te_8experts2parallel_multi_dist_optimizer_instances - gpt3_moe_mcore_te_tp4_ep2_etp2_pp2_resume_torch_dist_dist_optimizer Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: oliver könig <okoenig@nvidia.com>
Contributor
Author
|
/ok to test |
kajalj22
approved these changes
Apr 14, 2026
Contributor
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/24424777504 |
yangbofun
pushed a commit
to xlm-research/Megatron-LM
that referenced
this pull request
May 22, 2026
…er / torchrun) (NVIDIA#4298) Signed-off-by: oliver könig <okoenig@nvidia.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
yhgalaxy
pushed a commit
to yhgalaxy/Megatron-LM
that referenced
this pull request
Jun 17, 2026
…er / torchrun) (NVIDIA#4298) Signed-off-by: oliver könig <okoenig@nvidia.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: yhgalaxy <yhgalaxy@outlook.com>
jon-barker
pushed a commit
to jon-barker/Megatron-LM
that referenced
this pull request
Jul 10, 2026
…er / torchrun) (NVIDIA#4298) Signed-off-by: oliver könig <okoenig@nvidia.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Jon Barker <jbarker@aws-cmh-slurm-1-vscode-02.cm.cluster>
terminator123
pushed a commit
to 021ai/Megatron-LM
that referenced
this pull request
Aug 3, 2026
…er / torchrun) (NVIDIA#4298) Signed-off-by: oliver könig <okoenig@nvidia.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Introduces a
LAUNCHERtop-level key inmodel_config.yamlthat lets individual CI test cases opt intoft_launcher(fromnvidia-resiliency-ext) instead of the defaulttorchrun.torchrun— all existing test configs continue to work without any changes.LAUNCHER: ft_launcherin a test'smodel_config.yamlto switch to the fault-tolerance launcher.--nproc_per_node,--nnodes,--master_addr, etc.) are forwarded unchanged to both launchers sinceft_launcheris a drop-in torchrun replacement.Example
model_config.yamlsnippet to opt intoft_launcher:Resolves AUT-360
Test plan
LAUNCHERkey continue to usetorchrun(backward-compatible default via// "torchrun"yq fallback)LAUNCHER: ft_launcherinvokesft_launcherinstead ofpython -m torch.distributed.run🤖 Generated with Claude Code