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
Pre 2.10 version of allure-python did too much of thread isolation, leading to hooks added in one thread being inaccessible from another. Hooks responsible for flushing test results to the disk were registered in the main thread but the actual calls were made from a thread worker (a different thread), thus, no output files were emitted.
Starting from 2.10 thread isolation was weakened (see #647). Hooks are not thread isolated anymore and it became possible to run steps in parallel, but an attempt to use pytest-parallel results in the same error as in #697. As for now it looks like fixing #697 will fix this issue as well.
I'm submitting a ...
What is the current behavior?
I am running tests in paralell using pytest-paralell and test reports are not generated.
I have tried --workers and --tests-per-worker .
allure-python-commons==2.5.5
pytest==4.0.1
pytest-parallel==0.0.9
The text was updated successfully, but these errors were encountered: