-
Notifications
You must be signed in to change notification settings - Fork 25.7k
kill allow_complex_guards_as_runtime_asserts #161794
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/161794
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 87fec9d with merge base 71992dd ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D81334984 |
ea59544 to
ae4915d
Compare
Summary: [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Reviewed By: zhxchen17 Differential Revision: D81334984
|
This pull request was exported from Phabricator. Differential Revision: D81334984 |
ae4915d to
e89f01f
Compare
Summary: Pull Request resolved: pytorch#161794 [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Reviewed By: zhxchen17 Differential Revision: D81334984
Summary: Pull Request resolved: pytorch#161794 [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Reviewed By: zhxchen17 Differential Revision: D81334984
|
This pull request was exported from Phabricator. Differential Revision: D81334984 |
e89f01f to
87fec9d
Compare
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Summary: [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Differential Revision: D81334984 Pull Request resolved: pytorch#161794 Approved by: https://github.com/zhxchen17
Summary: [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Differential Revision: D81334984 Pull Request resolved: pytorch#161794 Approved by: https://github.com/zhxchen17
Summary: [reland] Since `allow_complex_guards_as_runtime_asserts` is now sync'd with `prefer_deferred_runtime_asserts_over_guards`, we can kill the former (especially since it was a export-only concept). Test Plan: updated tests Rollback Plan: Differential Revision: D81334984 Pull Request resolved: pytorch#161794 Approved by: https://github.com/zhxchen17
Summary:
[reland]
Since
allow_complex_guards_as_runtime_assertsis now sync'd withprefer_deferred_runtime_asserts_over_guards, we can kill the former (especially since it was a export-only concept).Test Plan:
updated tests
Rollback Plan:
Differential Revision: D81334984
cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv @voznesenskym @penguinwu @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @jiayisunx @chenyang78 @kadeng @chauhang @amjames @Lucaskabela