-
Notifications
You must be signed in to change notification settings - Fork 541
[JAX] L1_jax_distributed_test suit with individual executions #2321
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
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
db8a63f
fix
phu0ngng c17c5c1
added
phu0ngng 338155e
cmt out the test_multip grouped_gemm for now
phu0ngng cfb710b
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 25b14fa
rm e5m2 from test norm + MXFP8
phu0ngng aebaf81
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] e1e3fc3
restore unnessary changes
phu0ngng edfa6b0
Merge branch 'fix_jax_l1' of github.com:phu0ngng/TransformerEngine in…
phu0ngng 18c94c9
Merge branch 'main' into fix_jax_l1
phu0ngng 608ce90
cleanup
phu0ngng 2383ef1
Merge branch 'fix_jax_l1' of github.com:phu0ngng/TransformerEngine in…
phu0ngng 89207da
Merge branch 'main' into fix_jax_l1
phu0ngng 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
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
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
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
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.
logic: The grep pattern "FAILED" may not detect test failures. The test script at
test_multi_process_distributed_grouped_gemm.py:148-150callsjnp.allclose()without asserting the result, so tests pass even when values don't match. If the test were fixed to use assertions, failures would output tracebacks with "failed" (lowercase) not "FAILED" (uppercase).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.
I'm not sure on the exact error string reported here, but I do see
jnp.allcloseintest_multi_process_distributed_grouped_gemm.pyhere. From the docs, jnp.allclose returns a bool instead of asserting and the return value isn't used. Should we use ourassert_allclosefrom utils instead? Can be a separate PR as this PR is focused on the test failure reporting issueThere 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.
Yeah. I noticed it. This will be addressed in follow-up PR.