-
Notifications
You must be signed in to change notification settings - Fork 24.9k
[MTIA Aten Backend] Migrate any.all_out (example diff for tutorial) #159780
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
base: gh/andyanwang/39/base
Are you sure you want to change the base?
Conversation
Differential Revision: [D79524919](https://our.internmc.facebook.com/intern/diff/D79524919/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/159780
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (3 Unrelated Failures)As of commit 732491e with merge base 8bc843a ( UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Differential Revision: [D79524919](https://our.internmc.facebook.com/intern/diff/D79524919/) ghstack-source-id: 300421432 Pull Request resolved: #159780
This pull request was exported from Phabricator. Differential Revision: D79524919 |
Attention! native_functions.yaml was changedIf you are adding a new function or defaulted argument to native_functions.yaml, you cannot use it from pre-existing Python frontend code until our FC window passes (two weeks). Split your PR into two PRs, one which adds the new C++ functionality, and one that makes use of it from Python, and land them two weeks apart. See https://github.com/pytorch/pytorch/wiki/PyTorch's-Python-Frontend-Backward-and-Forward-Compatibility-Policy#forwards-compatibility-fc for more info. Caused by: |
…tutorial)" Differential Revision: [D79524919](https://our.internmc.facebook.com/intern/diff/D79524919/) # Context See the first PR #153670 # This diff Migrate any.all_out to in-tree. We can use this diff as an example for in-tree registration. [ghstack-poisoned]
Pull Request resolved: #159780 # Context See the first PR #153670 # This diff Migrate any.all_out to in-tree. We can use this diff as an example for in-tree registration. Differential Revision: [D79524919](https://our.internmc.facebook.com/intern/diff/D79524919/) ghstack-source-id: 300591646
This pull request was exported from Phabricator. Differential Revision: D79524919 |
Stack from ghstack (oldest at bottom):
Differential Revision: D79524919
Context
See the first PR #153670
This diff
Migrate any.all_out to in-tree.
We can use this diff as an example for in-tree registration.
cc @egienvalue