-
Notifications
You must be signed in to change notification settings - Fork 24.3k
[FlexAttention] Remove old constraint that was causing assert failure #151521
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/151521
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 33 PendingAs of commit b70a871 with merge base 2c27597 ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@mandroid6 just a heads up I imagine there is some overlap between this and the TMA work |
…ert failure" # Summary Fixes: #148827 This one is strange, I could have sworn this was a real constraint, but I verified and did some performance checks and this constraint isn't required. cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy chenyang78 kadeng muchulee8 amjames chauhang aakhundov Chillee yanboliang BoyuanFeng [ghstack-poisoned]
@pytorchbot cherry-pick --onto release/2.7 -c critical |
1 similar comment
@pytorchbot cherry-pick --onto release/2.7 -c critical |
Stack from ghstack (oldest at bottom):
Summary
Fixes: #148827
This one is strange, I could have sworn this was a real constraint, but I verified and did some performance checks and this constraint isn't required.
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @chenyang78 @kadeng @muchulee8 @amjames @chauhang @aakhundov @Chillee @yanboliang @BoyuanFeng