-
Notifications
You must be signed in to change notification settings - Fork 25.8k
record_function: remove legacy internal operators #72303
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
[ghstack-poisoned]
CI Flow Status⚛️ CI FlowRuleset - Version:
|
🔗 Helpful links
❌ 1 New FailuresAs of commit a127895 (more details on the Dr. CI page): Expand to see more
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages
|
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
…emove legacy internal operators" [ghstack-poisoned]
[ghstack-poisoned]
…l operators" [ghstack-poisoned]
|
@peterbell10 your PR has been successfully reverted. |
This reverts commit 0be84bb. Reverted #72303 on behalf of https://github.com/izaitsevfb due to Apparently _record_function_enter is still used internally at Meta in several places and in lots of internal tests. ([comment](#72303 (comment)))
These operators have not been used since pytorch#76420 but were preserved for TorchScript backward compatibility Pull Request resolved: pytorch#72303 Approved by: https://github.com/albanD ghstack dependencies: pytorch#104535
)" This reverts commit 0be84bb. Reverted pytorch#72303 on behalf of https://github.com/izaitsevfb due to Apparently _record_function_enter is still used internally at Meta in several places and in lots of internal tests. ([comment](pytorch#72303 (comment)))
These operators have not been used since pytorch#76420 but were preserved for TorchScript backward compatibility Pull Request resolved: pytorch#72303 Approved by: https://github.com/albanD ghstack dependencies: pytorch#104535
)" This reverts commit 0be84bb. Reverted pytorch#72303 on behalf of https://github.com/izaitsevfb due to Apparently _record_function_enter is still used internally at Meta in several places and in lots of internal tests. ([comment](pytorch#72303 (comment)))
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
These operators have not been used since #76420 but were preserved for TorchScript backward compatibility [ghstack-poisoned]
These operators have not been used since #76420 but were preserved for TorchScript backward compatibility 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 [ghstack-poisoned]
[ghstack-poisoned]
…internal operators" [ghstack-poisoned]
These operators are not used in eager since #76420, and are only retained for TorchScript BC which has now expired. BC-breaking message: TorchScript exported models that use `torch.autograd.profiler.record_function` and were exported on PyTorch < `2.0` will no longer be loadable. Please re-export your model with 2.0 or newer. [ghstack-poisoned]
Stack from ghstack (oldest at bottom):
These operators are not used in eager since #76420, and are only retained for TorchScript BC which has now expired.
BC-breaking message:
TorchScript exported models that use
torch.autograd.profiler.record_functionand were exported on PyTorch <2.0will no longer be loadable. Please re-export your model with 2.0 or newer.