-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Fix test_parity xfail for sigmoid #134253
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/134253
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 0669c68 with merge base b417e32 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Looks good, complex support was possible, but for some reason not instantiated.
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.
nice!
Pull Request resolved: #134344 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: #134253
Previously, error messages were expected to be string equivalent to error messages thrown by the ref function. This check fails for dozens of torch functions, and doesn't appear to add much value for the end user. This commit removes this check. Pull Request resolved: #134251 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: #134253, #134344
Pull Request resolved: #134253 Approved by: https://github.com/amjames, https://github.com/janeyx99
Pull Request resolved: #134344 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: #134253
Previously, error messages were expected to be string equivalent to error messages thrown by the ref function. This check fails for dozens of torch functions, and doesn't appear to add much value for the end user. This commit removes this check. Pull Request resolved: #134251 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: #134253, #134344
Pull Request resolved: pytorch#134253 Approved by: https://github.com/amjames, https://github.com/janeyx99
Pull Request resolved: pytorch#134344 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: pytorch#134253
…h#134251) Previously, error messages were expected to be string equivalent to error messages thrown by the ref function. This check fails for dozens of torch functions, and doesn't appear to add much value for the end user. This commit removes this check. Pull Request resolved: pytorch#134251 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: pytorch#134253, pytorch#134344
Pull Request resolved: pytorch#134344 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: pytorch#134253
…h#134251) Previously, error messages were expected to be string equivalent to error messages thrown by the ref function. This check fails for dozens of torch functions, and doesn't appear to add much value for the end user. This commit removes this check. Pull Request resolved: pytorch#134251 Approved by: https://github.com/amjames, https://github.com/janeyx99 ghstack dependencies: pytorch#134253, pytorch#134344
Stack from ghstack (oldest at bottom):
cc @crcrpar @mcarilli @janeyx99