-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Change default torch_function behavior to be disabled when torch_dispatch is defined (take 2) #120632
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/120632
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit 337e6b8 with merge base 7b4f70e ( BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
yoloooo
@JackCaoG is there an easy way for me to run this failing xla test on a cpu linux machine?
|
Yea I can add that to |
7365484
to
aad5b12
Compare
@JackCaoG where I can know if the PR you did is already included in PT trunk? Or anything I should do to make your PR in xla included for this PR? |
You can check https://github.com/pytorch/xla/tree/master/.circleci#coodinating-merges-for-breaking-pytorch-prs for detail but pretty much you can update https://github.com/pytorch/pytorch/blob/main/.github/ci_commit_pins/xla.txt to the head of the pt/xla. I checked that file and it seems like pin was updated today so if you rebase this should just work. |
aad5b12
to
337e6b8
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 |
…atch is defined (take 2) (#120632) This does not introduce a new test but is tested by checking that all the classes we already have still behave as before now that they don't explicitly disable torch_function. Pull Request resolved: #120632 Approved by: https://github.com/ezyang
This does not introduce a new test but is tested by checking that all the classes we already have still behave as before now that they don't explicitly disable torch_function.
cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @ezyang @gchanan @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @aakhundov