-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[JIT] Fix torch.jit.is_tracing() #42486
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
**Summary** This commit fixes a small bug in which `torch.jit.is_tracing()` returns `torch._C.is_tracing`, the function object, instead of calling the function and returning the result. **Test Plan** Continuous integration? **Fixes** This commit fixes #42448. [ghstack-poisoned]
**Summary** This commit fixes a small bug in which `torch.jit.is_tracing()` returns `torch._C.is_tracing`, the function object, instead of calling the function and returning the result. **Test Plan** Continuous integration? **Fixes** This commit fixes #42448. ghstack-source-id: f78319d Pull Request resolved: #42486
💊 CI failures summary and remediationsAs of commit 75c25ef (more details on the Dr. CI page):
❄️ 2 failures tentatively classified as flakybut reruns have not yet been triggered to confirm:
|
|
@SplitInfinity merged this pull request in 29700c0. |
Stack from ghstack:
Summary
This commit fixes a small bug in which
torch.jit.is_tracing()returnstorch._C.is_tracing, the function object, instead of calling thefunction and returning the result.
Test Plan
Continuous integration?
Fixes
This commit fixes #42448.
Differential Revision: D22911062