-
Notifications
You must be signed in to change notification settings - Fork 603
Pull c10 headers directly from PyTorch internally, not from the c10 mirror #11800
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
Pull c10 headers directly from PyTorch internally, not from the c10 mirror #11800
Conversation
…irror Previously, both internal and external worlds got ExecuTorch's pinned version of PyTorch. Now external is the same, but internal gets its monorepo behavior. PyTorch guarantees backward compatibility (i.e., not breaking the builds of existing PyTorch users), so our ExecuTorch code that works with pinned PyTorch should also automatically work with internal PyTorch. (bc breaks will be difficult, but that's inherent to bc breaks.) Differential Revision: [D76832520](https://our.internmc.facebook.com/intern/diff/D76832520/) [ghstack-poisoned]
…irror Previously, both internal and external worlds got ExecuTorch's pinned version of PyTorch. Now external is the same, but internal gets its monorepo behavior. PyTorch guarantees backward compatibility (i.e., not breaking the builds of existing PyTorch users), so our ExecuTorch code that works with pinned PyTorch should also automatically work with internal PyTorch. (bc breaks will be difficult, but that's inherent to bc breaks.) Differential Revision: [D76832520](https://our.internmc.facebook.com/intern/diff/D76832520/) ghstack-source-id: 291387183 Pull Request resolved: #11800
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11800
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit fd9379d with merge base 5136175 ( BROKEN TRUNK - The following job 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. |
This pull request was exported from Phabricator. Differential Revision: D76832520 |
test-moshi-linux was broken on trunk around the time this was sent out |
79953b7
into
gh/swolchok/463/base
…irror (#11835) This PR was created by the merge bot to help merge the original PR into the main branch. ghstack PR number: #11800 by @swolchok ^ Please use this as the source of truth for the PR details, comments, and reviews ghstack PR base: https://github.com/pytorch/executorch/tree/gh/swolchok/463/base ghstack PR head: https://github.com/pytorch/executorch/tree/gh/swolchok/463/head Merge bot PR base: https://github.com/pytorch/executorch/tree/main Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/swolchok/463/orig @diff-train-skip-merge Co-authored-by: Scott Wolchok <[email protected]>
Stack from ghstack (oldest at bottom):
Previously, both internal and external worlds got ExecuTorch's pinned version of PyTorch. Now external is the same, but internal gets its monorepo behavior. PyTorch guarantees backward compatibility (i.e., not breaking the builds of existing PyTorch users), so our ExecuTorch code that works with pinned PyTorch should also automatically work with internal PyTorch. (bc breaks will be difficult, but that's inherent to bc breaks.)
Differential Revision: D76832520