-
Notifications
You must be signed in to change notification settings - Fork 719
[PyTorch] Batch CP attention tests in single torchrun to amortize NCC… #2965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sudhakarsingh27
wants to merge
8
commits into
NVIDIA:main
Choose a base branch
from
sudhakarsingh27:sudhakars/cp_test_batching_pr
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
6355f62
[PyTorch] Batch CP attention tests in single torchrun to amortize NCC…
sudhakarsingh27 686e76b
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] fc00d4c
[PyTorch] Broaden launch-error catch in CP batch dispatch
sudhakarsingh27 642e363
[PyTorch] Fix FP8 cascade failures and skip divergence in CP batch tests
sudhakarsingh27 e591e02
[PyTorch] Improve encapsulation of CP batch test infra
sudhakarsingh27 de9ab3d
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 2090f14
Merge branch 'main' of github.com:NVIDIA/TransformerEngine into sudha…
51d0ba5
Merge branch 'main' into sudhakars/cp_test_batching_pr
sudhakarsingh27 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a non-zero rank fails inside
_run_single_config, its traceback is captured in that rank's localerrvariable but never transmitted to rank 0. Theall_reducepropagates theok=0flag correctly, but rank 0 only records"Failed on a non-zero rank (see subprocess stderr for traceback)". That guidance is wrong: because_run_single_configcatches the exception on rank 1, rank 1 exits cleanly andtorchrunexits with code 0 — there is no traceback in subprocess stderr. A developer investigating the failure would find nothing there.This is a regression from the original non-batched flow where rank 1's uncaught exception printed directly to
torchrun's stderr and was captured byrun_distributed. A minimal fix is to have the failing rank(s) print their traceback tosys.stderrbefore returning from_run_single_config, so it appears intorchrun's captured output even when the process exits cleanly.