The plugin works around calling pytest_runtest_protocol hook of pytest. It does not signal to new forks when test processing starting (lesser problem) and does not signal when test processing ended (greater problem). This makes impossible to gracefully finish other plugins which work during the whole pytest lifecycle. E.G. in my project I can't catch the moment when to upload the last log batch on our server. Thus I constantly lose the tail of logs if my users use pytest-parallel. And I can't also use fully async client by the same reason. I won't get the whole batch of test items because pytest-parallel terminates child process execution instantly.
The situation makes me deprecate using pytest-parallel along with my plugin. Unless pytest-parallel provide necessary options.
The plugin works around calling
pytest_runtest_protocolhook ofpytest. It does not signal to new forks when test processing starting (lesser problem) and does not signal when test processing ended (greater problem). This makes impossible to gracefully finish other plugins which work during the wholepytestlifecycle. E.G. in my project I can't catch the moment when to upload the last log batch on our server. Thus I constantly lose the tail of logs if my users usepytest-parallel. And I can't also use fully async client by the same reason. I won't get the whole batch of test items becausepytest-parallelterminates child process execution instantly.The situation makes me deprecate using
pytest-parallelalong with my plugin. Unlesspytest-parallelprovide necessary options.