-
Notifications
You must be signed in to change notification settings - Fork 572
fix: fallback to dot_product for autoselected attention on CPU to prevent Tokamax NotImplementedError
#4617
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
chiajunglien
wants to merge
1
commit into
AI-Hypercomputer:main
Choose a base branch
from
CIeNET-International:emma/fix-conversion
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.
+1
−0
Open
Changes from all commits
Commits
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
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.
this change gonna silently twist all results using AOT on CPU platform
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 doubt this change can pass https://github.com/AI-Hypercomputer/maxtext/blob/main/tests/integration/aot_identical_test.py
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.
somehow aot identical test does not show in https://github.com/AI-Hypercomputer/maxtext/actions/runs/30232605541/job/89875651384?pr=4617
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.
Hi @NuojCheng, thanks for the review! I've double-checked the AOT compilation behavior, and this change works safely without twisting results.
1. AOT correctly bypasses the fallback:
Even when cross-compiling on a CPU host, AOT (via
train_compile.py) usesget_topology_desc(platform="tpu")to generate mock devices. These mock devices strictly retaindevice.platform == "tpu". Thus,target_hardwareremains"tpu", properly preserving theflashorautoselectedkernels without triggering a fallback todot_product.2.
aot_identical_test.pypasses flawlessly:I just ran the test manually on my TPU VM and can confirm the generated HLO graphs remain identical and it passes perfectly:
tests/integration/aot_identical_test.py::AotHloIdenticalTest::test_default_hlo_match PASSEDLog: https://paste.googleplex.com/4608946768838656
If it’s missing in recent CI job logs, it’s likely because the test classes are wrapped with
@pytest.mark.skip_on_tpu7x. If a GitHub Action runner happens to execute on a Trillium (tpu7x) node, Pytest naturally skips it.Let me know if this clears up the concerns!