-
Notifications
You must be signed in to change notification settings - Fork 23
Add default exclusion of slow tests in pytest #1831
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
|
View rendered docs @ https://intelpython.github.io/dpnp/index.html |
|
about my last commit |
antonwolfy
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.
Thank you @vlad-perevezentsev, the change is very helpful and makes the tests more stable.
The filterwarnings marker can be added separately.
I will keep |
* Register slow and multi_gpu marks for pytest * Add default exclusion of slow tests in pytest * Add @testing.slow for test_matmul_large * Remove test skip for dpnp.power * Remove unused import in test_sumprod.py * Add filterwarnings to markers * Remove -p no:warnings from pytest addopts * Undo commit with remove -p no:warnings --------- Co-authored-by: Anton <[email protected]> ab5ed63
This PR suggests to exclude running slow tests (marked as slow) when pytest is called by default and to register custom markers such as
slowandmulti_gpu.These changes will help to avoid spontaneous hangs in internal CI since some tests are decorated by
@testing.slowwhich is not implemented yet.It is assumed that such tests (usually using huge data) should perform computation on multiple devices to reduce the computation load. Internal CI contains one device and running such tests causes spontaneous hangs.
To run all tests including those marked as slow (
@testing.slow) usepytest -m "not slow or slow"Also removes test skipping for
dpnp.power()due to using the latest OneAPI compiler for coverage GitHub Action #1777