-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Removes nonzero method warning #51618
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
💊 CI failures summary and remediationsAs of commit e2b5868 (more details on the Dr. CI page):
This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions to the (internal) Dr. CI Users group. |
facebook-github-bot
left a comment
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.
@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
| warnings.simplefilter("always") | ||
| torch.nonzero(t) | ||
| t.nonzero() | ||
| self.assertEqual(len(w), 0) |
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.
should this be unindented?
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.
I don't think it matters?
Codecov Report
@@ Coverage Diff @@
## master #51618 +/- ##
==========================================
- Coverage 80.86% 80.86% -0.01%
==========================================
Files 1942 1942
Lines 211466 211466
==========================================
- Hits 171006 171005 -1
- Misses 40460 40461 +1 |
Fixes #44284
#45413 incorrectly left this only partially fixed because it did not update the separate list of method signatures that were deprecated. This PR correctly fixes #44284. A test is added for the behavior, but until the WARN_ONCE flag is added it's toothless.