-
Notifications
You must be signed in to change notification settings - Fork 25.7k
remove componentwise comparison of complex values in torch.testing.assert_close #63841
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
…sert_close [ghstack-poisoned]
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 4e8c80e (more details on the Dr. CI page):
🕵️ 5 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
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.
Cool simplification but maybe a little too aggressive with the conjugate bit test? I also have a name suggestion (naming things is hard but XXX seems easy to improve on)
|
@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
….testing.assert_close" Closes #61906. cc @ezyang @gchanan Differential Revision: [D30633526](https://our.internmc.facebook.com/intern/diff/D30633526) [ghstack-poisoned]
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.
Cool!
|
@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Stack from ghstack:
Closes #61906.
cc @ezyang @gchanan
Differential Revision: D30633526