You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use pytest-xdist in mne-lsl: mne-tools/mne-lsl#229
However, in the test suite, some test need to be run while no other test are running because they spawn network resources which might be pick-up by other tests. Example:
In this example, test2 would be affected by test1 run in a different worker.
To avoid this problem, I would like new markers from pytest-xdist to mark which test should not be distributed and should be run through --dist no, either before or after all the other tests distributed to workers.
e.g.
@pytest.mark.no_xdist
def test2(...):
My current alternative idea is to create this marker and to run 2 separate pytest command.
The text was updated successfully, but these errors were encountered:
The difference between this request and my alternative lies that developers won't accidently run the test suit with xdist and without the -m "not no_xdist". The -m flag is not needed anymore as xdist will handle dispatching correctly.
OK thank you! Could that be a feature request then? Some test need to be run in isolation; and preventing an entire test suite to run on xdist because of a minority is disappointing.
If there is no plan/desire to add this feature, feel free to close this issue!
I would like to use
pytest-xdist
inmne-lsl
: mne-tools/mne-lsl#229However, in the test suite, some test need to be run while no other test are running because they spawn network resources which might be pick-up by other tests. Example:
In this example,
test2
would be affected bytest1
run in a different worker.To avoid this problem, I would like new markers from
pytest-xdist
to mark which test should not be distributed and should be run through--dist no
, either before or after all the other tests distributed to workers.e.g.
My current alternative idea is to create this marker and to run 2 separate
pytest
command.The text was updated successfully, but these errors were encountered: