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
It appears that all pylint tests are executed on all workers in parallel, moreover, they are executed before the regular tests are executed, which makes the run overall 4 times slower in a distributed test suite.
I am not sure why, but I have also noticed that when running tests in a distributed fashion then tests don't get skipped as they usually are (on the second run), moreover duplicate-code errors don't appear reliably either. I understand that originally the idea was to run pylint tests independently of pytest's collection in one run, but it seems that this is not working as expected either.
The text was updated successfully, but these errors were encountered:
It seems that
pytest-pylint
is not playing very well withpytest-xdist
. On a relatively small project:It appears that all pylint tests are executed on all workers in parallel, moreover, they are executed before the regular tests are executed, which makes the run overall 4 times slower in a distributed test suite.
I am not sure why, but I have also noticed that when running tests in a distributed fashion then tests don't get skipped as they usually are (on the second run), moreover duplicate-code errors don't appear reliably either. I understand that originally the idea was to run pylint tests independently of pytest's collection in one run, but it seems that this is not working as expected either.
The text was updated successfully, but these errors were encountered: