-
Notifications
You must be signed in to change notification settings - Fork 26.3k
remove assert_allclose from torch.testing #87974
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
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/87974
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 FailuresAs of commit 2ae120b: The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
cc albanD [ghstack-poisoned]
cc albanD [ghstack-poisoned]
cc albanD [ghstack-poisoned]
cc albanD [ghstack-poisoned]
| @@ -1,5 +1,5 @@ | |||
| """ | |||
| This file only exists since `torch.testing.assert_allclose` is deprecated, but used extensively throughout the tests in | |||
| This file only exists since `torch.testing.assert_allclose` was removed, but used extensively throughout the tests in | |||
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 doc update
mruberry
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.
Nice to have the deprecations finalized!
|
@pytorchbot merge -f "CI failures are unrelated" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Yeah, this is due to: Line 10 in 35be73d
By default, pytest does show the warnings though. So unless users have manually silenced their pytest warnings (like pytorch), they should have properly seen the deprecation message |
|
From #87969 (comment):
The RFC that lead to this deprecation is in #61844.
If you look at the diff into the deleted file |
tbh I use the direct |
|
This PR breaks downstream code such as https://github.com/kornia/kornia/blob/v0.6.8/kornia/testing/__init__.py#L254 |
|
@xuzhao9 sorry about that. I'm a bit confused as the code there seem to imply that this case is only used for PT <1.9 ? |
Summary: `assert_close` is preferred over `assert_allclose`: pytorch/pytorch#61844 The `assert_allclose` was removed yesterday in pytorch/pytorch#87974, causing test to fail, eg. https://github.com/facebookresearch/d2go/actions/runs/3389194553/jobs/5632021291 Reviewed By: sstsai-adl Differential Revision: D41000306 fbshipit-source-id: 8c513a3f570712452367f3210cf3644fb2b94666
|
@albanD The authors are aware of this change and is discussing a mitigation: kornia/kornia#1981 Yes, currently kornia will only work on 1.9 > pytorch >=1.8.1, but it seems authors are working on a fix. |
Summary: Pull Request resolved: #409 `assert_close` is preferred over `assert_allclose`: pytorch/pytorch#61844 The `assert_allclose` was removed yesterday in pytorch/pytorch#87974, causing test to fail, eg. https://github.com/facebookresearch/d2go/actions/runs/3389194553/jobs/5632021291 Reviewed By: sstsai-adl Differential Revision: D41000306 fbshipit-source-id: 7bd1cb9d5edf0a4609a909e2283df411bcabdf13
|
Unfortunately, we need to revert this PR. We have many references to I will follow up on the task to update all internal reference to @pytorchbot revert -m "Internal breakages from method removal" -c ghfirst |
|
@pytorchbot successfully started a revert job. Check the current status here. |
|
@pmeier your PR has been successfully reverted. |
This reverts commit 5669e10. Reverted #87974 on behalf of https://github.com/mehtanirav due to Internal breakages from method removal
|
cc: @albanD on the revert. |
See pytorch#87969 or pytorch#86586 for the reasoning. Pull Request resolved: pytorch#87974 Approved by: https://github.com/mruberry
This reverts commit 5669e10. Reverted pytorch#87974 on behalf of https://github.com/mehtanirav due to Internal breakages from method removal
After our failed attempt to remove `assert_allclose` in #87974, we decided to add it to the documentation after all. Although we drop the expected removal date, the function continues to be deprecated in favor of `assert_close`. [ghstack-poisoned]
After our failed attempt to remove `assert_allclose` in #87974, we decided to add it to the documentation after all. Although we drop the expected removal date, the function continues to be deprecated in favor of `assert_close`. [ghstack-poisoned]
After our failed attempt to remove `assert_allclose` in #87974, we decided to add it to the documentation after all. Although we drop the expected removal date, the function continues to be deprecated in favor of `assert_close`. Pull Request resolved: #89526 Approved by: https://github.com/mruberry
See pytorch#87969 or pytorch#86586 for the reasoning. Pull Request resolved: pytorch#87974 Approved by: https://github.com/mruberry
This reverts commit 5669e10. Reverted pytorch#87974 on behalf of https://github.com/mehtanirav due to Internal breakages from method removal
After our failed attempt to remove `assert_allclose` in pytorch#87974, we decided to add it to the documentation after all. Although we drop the expected removal date, the function continues to be deprecated in favor of `assert_close`. Pull Request resolved: pytorch#89526 Approved by: https://github.com/mruberry
Stack from ghstack (oldest at bottom):
See #87969 or #86586 for the reasoning.
cc @albanD