Skip to content

Revert "[CUDA] Enable XQA by default for FP16/BF16 GQA (#29046)"#29217

Closed
hariharans29 wants to merge 1 commit into
mainfrom
hari/fix_cuda_pipeline
Closed

Revert "[CUDA] Enable XQA by default for FP16/BF16 GQA (#29046)"#29217
hariharans29 wants to merge 1 commit into
mainfrom
hari/fix_cuda_pipeline

Conversation

@hariharans29

Copy link
Copy Markdown
Member

Description

This reverts commit 6be94de.

It is currently breaking a test in Linux x64 CUDA CI:

image

This test itself was introduced in PR #29002 which was merged last night but its CI ran 5 days ago and that test passed on CI. When the PR #29046 was in CI - that particular test did not exist and so #29046 also "passed" CI. But these 2 PRs in combination now break main branch and block other PR merges.

Sample PRs where it fails the Linux CUDA CIs:

#29200
#29207

Motivation and Context

Unblock PR merges into main as Linux CUDA CI is red in main branch now

@hariharans29 hariharans29 requested a review from tianleiwu June 22, 2026 20:59
@hariharans29

Copy link
Copy Markdown
Member Author

Closing as the root cause for main branch CI failure is NOT enabling XQA by default. It seems like the tfailing test is using fp32 inputs which is falling back to CPU and exposing the bug that it being fixes by #29069

@hariharans29 hariharans29 deleted the hari/fix_cuda_pipeline branch June 22, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant