-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Nvfuser cpp api deprecation attempt 2 #110881
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
Nvfuser cpp api deprecation attempt 2 #110881
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/110881
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit cd8ba03 with merge base 4b881b0 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
At least in the repro in #110857 , we are not throwing any warning when users are just running vanilla torchscript. |
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.
@jjsjann123 says the repro doesn't throw warnings now, so LGTM
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.
Thank you!
|
@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 |
This is to follow up with upstream pytorch's code removal in pytorch/pytorch#110881
attempting to re-try #110318 deprecating nvfuser c++ API
warning has been updated to TORCH_WARN_ONCE;
Warning thrown inside torch::jit::fuser::cuda::isEnabled() is turned off and will be deprecated when we pulled out TorchScript integration in the follow up PR.