hide top-level test functions from pytest's traceback #58915
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
History: - It was included for internal helper functions in the initial proposal in #53820 - It was removed in #54780, since it is not honored when used with `pytest`'s `--tb=native`, which is the default for PyTorch Since PyTorch shouldn't be the only user of `assert_(equal|close)` we add it here to the top-level functions `assert_(equal|close)`. If `pytest` is used without `--tb=native`, the traceback for ```python assert torch.eq(actual, expected), "Tensors are not equal!" torch.testing.assert_equal(actual, expected) ``` looks the same, making it more concise. [ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit e59d862 (more details on the Dr. CI page and at hud.pytorch.org/pr/58915): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 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. |
This was referenced May 25, 2021
rgommers
added
the
module: testing
History: - It was included for internal helper functions in the initial proposal in #53820 - It was removed in #54780, since it is not honored when used with `pytest`'s `--tb=native`, which is the default for PyTorch Since PyTorch shouldn't be the only user of `assert_(equal|close)` we add it here to the top-level functions `assert_(equal|close)`. If `pytest` is used without `--tb=native`, the traceback for ```python assert torch.eq(actual, expected), "Tensors are not equal!" torch.testing.assert_equal(actual, expected) ``` looks the same, making it more concise. [ghstack-poisoned]
History: - It was included for internal helper functions in the initial proposal in #53820 - It was removed in #54780, since it is not honored when used with `pytest`'s `--tb=native`, which is the default for PyTorch Since PyTorch shouldn't be the only user of `assert_(equal|close)` we add it here to the top-level functions `assert_(equal|close)`. If `pytest` is used without `--tb=native`, the traceback for ```python assert torch.eq(actual, expected), "Tensors are not equal!" torch.testing.assert_equal(actual, expected) ``` looks the same, making it more concise. [ghstack-poisoned]
History: - It was included for internal helper functions in the initial proposal in #53820 - It was removed in #54780, since it is not honored when used with `pytest`'s `--tb=native`, which is the default for PyTorch Since PyTorch shouldn't be the only user of `assert_(equal|close)` we add it here to the top-level functions `assert_(equal|close)`. If `pytest` is used without `--tb=native`, the traceback for ```python assert torch.eq(actual, expected), "Tensors are not equal!" torch.testing.assert_equal(actual, expected) ``` looks the same, making it more concise. [ghstack-poisoned]
|
@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack:
msgintorch.testing.assert_close#60254 tests for diagnostics in callablemsgintorch.testing.assert_closetorch.testing.assert_close#60163 update docstring examples oftorch.testing.assert_closetorch.testing.assert_closein case of mismatching values #60091 Improve error messages oftorch.testing.assert_closein case of mismatching valuestorch.testing.assert_close#58918 make assert_equal an example how to partialtorch.testing.assert_closeHistory:
in initial draft for assert_tensors_(equal|allclose) in torch.testing #53820
pytest's--tb=native, which is the default for PyTorchSince PyTorch shouldn't be the only user of
assert_(equal|close)weadd it here to the top-level functions
assert_(equal|close). Ifpytestis used without--tb=native, the traceback forlooks the same, making it more concise.
Differential Revision: D29259406