-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[triton_op] fix autotuning #131363
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
[triton_op] fix autotuning #131363
Conversation
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/131363
Note: Links to docs will display an error until the docs builds have been completed. ❌ 5 Cancelled Jobs, 1 Unrelated FailureAs of commit fe86609 with merge base 102d8e5 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests ghstack-source-id: 3768c34 Pull Request resolved: #131363
|
@pytorchbot merge -f "lint looks unrelated?" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchmergebot revert -c ignoredsignal -m "This was a tricky one, but looking at the code it's the change to torch/fx/node.py that triggered the type violation errors. Reverting since this is now breaking trunk" |
|
@pytorchbot successfully started a revert job. Check the current status here. |
|
@zou3519 your PR has been successfully reverted. |
This reverts commit 154f274. Reverted #131363 on behalf of https://github.com/ZainRizvi due to This was a tricky one, but looking at the code it's the change to torch/fx/node.py that triggered the type violation errors. Reverting since this is now breaking trunk ([comment](#131363 (comment)))
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang [ghstack-poisoned]
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests ghstack-source-id: b5fbeaf Pull Request resolved: #131363
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang [ghstack-poisoned]
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests ghstack-source-id: 95ca95f Pull Request resolved: #131363
|
@pytorchbot merge -f "rocm infinite queue" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests Pull Request resolved: pytorch#131363 Approved by: https://github.com/oulgen
This reverts commit 154f274. Reverted pytorch#131363 on behalf of https://github.com/ZainRizvi due to This was a tricky one, but looking at the code it's the change to torch/fx/node.py that triggered the type violation errors. Reverting since this is now breaking trunk ([comment](pytorch#131363 (comment)))
The problem was we were shoving SymInts into the constant_args side table. The root problem is that torch.fx.node.base_types, which we use to determine what can be put in the graph, doesn't actually have SymInt in it. This PR fixes base_types to include SymInt. Test Plan: - tests Pull Request resolved: pytorch#131363 Approved by: https://github.com/oulgen, https://github.com/justinchuby
Stack from ghstack (oldest at bottom):
The problem was we were shoving SymInts into the constant_args side
table. The root problem is that torch.fx.node.base_types, which we use
to determine what can be put in the graph, doesn't actually have SymInt
in it. This PR fixes base_types to include SymInt.
Test Plan:
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang