-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Unittests] Added a meta-test for tvm.testing.fixture behavior in case of a broken fixture. #8343
Conversation
def test_uses_broken_cached_fixture(self, broken_cached_fixture): | ||
type(self).num_uses_broken_cached_fixture += 1 | ||
|
||
def test_num_uses_cached(self): |
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.
if we parallelize testing, will this inter-test dependency work?
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.
Currently, it will not. We'd need to also add a call to pytest_xdist_make_scheduler
(example stack overflow post) in order to force these tests to be run in order on a single node.
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.
As mentioned in our conversation yesterday, I've added a comment regarding pytest-xdist and the link to the above stackoverflow post to this PR, so that it will be easier to find if/when we parallelize the testing.
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.
this seems like a reasonably easy thing to do. thanks @Lunderberg !
…e of a broken fixture. In these cases, the test function should be marked as failing the setup, and should not run. This is pytest's default behavior, and should work whether or not a fixture is cached.
b0b0551
to
770ebc1
Compare
…e of a broken fixture. (apache#8343) In these cases, the test function should be marked as failing the setup, and should not run. This is pytest's default behavior, and should work whether or not a fixture is cached. Co-authored-by: Eric Lunderberg <[email protected]>
…e of a broken fixture. (apache#8343) In these cases, the test function should be marked as failing the setup, and should not run. This is pytest's default behavior, and should work whether or not a fixture is cached. Co-authored-by: Eric Lunderberg <[email protected]>
In these cases, the test function should be marked as failing the setup, and should not run. This is pytest's default behavior, and should work whether or not a fixture is cached.