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.
test: pin Llama3 TurboAttention GQA layout (PRPUNDIT-20) #1090
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
test: pin Llama3 TurboAttention GQA layout (PRPUNDIT-20) #1090
Changes from all commits
54d8bc0File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
TestIntel PR Steward: Thanks — I looked at whether this test can actually see the failure mode you describe.
This test instantiates
Attention(llama3_args)directly with no tensor-parallel mesh or sharding applied anywhere in the test (noDeviceMesh, noparallelize_module, no distributed process group).wq/wk/wvare therefore always built with the globaln_heads/n_kv_headsfromllama3_args, soxq.view(bs, seqlen, -1, head_dim)always resolves tollama3_args.n_headshere — the-1and the global arg are the same number in this unit test's scope. So the assertions againstllama3_args.n_heads/n_kv_headsare correct for what this test actually exercises.Deriving the expected counts from
wq(x)/wk(x)/wv(x)shapes instead would be a defensive nice-to-have (guards against a future test that does add TP sharding), but it doesn't change correctness today, and this PR's scope is pinning the existing GQA-layout behavior for the test gap (PRPUNDIT-20), not adding TP coverage. Leaving the assertions as-is; happy to revisit if a follow-up test adds actual sharded execution.Uh oh!
There was an error while loading. Please reload this page.