Andrea Bisello

@mscheltienne for me it works adding sequencial tests in a specific group (by mark) and then execute pytest with --dist loadgroup as described here https://pytest-xdist.readthedocs.io/en/latest/distribution.html#running-tests-across-multiple-cpus

@mscheltienne yeah pack all the test that you want to execute sequentially in the same worker using the same group, all the rest will be distributed to all the other...

i never found a solution for this, so when i need to obtain test results as fast as possible, i use xdist, when i need logs, i don't use xdist,...

as any worker logs his logs, with this hook (to be adapted) we join all the workers logs in a single file. ``` def pytest_sessionfinish(session): lista = [] nome_file_log =...

@RonnyPfannschmidt Thanks for your anwer. What about acquisition/provisioning? can you explain to me better? thanks

thanks @RonnyPfannschmidt so a feature that mark test as to be not parallelized by xdist but to be executed sequentially can be a good feature for xdist?

@kurt-cb thanks. I was also thinking that i some fixture regardings workers existed, i could inject that fixture into the test and put the tast in wait until "other" workers...

one year 7 months later, someone has found a workaround? pytest-xdist is too much important for me ( many thanks pytest-xdist plugin developers

> Hmm on the other hand, I just noticed that not using `log_cli`, but just normal logging capture, works as expected: > > ```ini > [pytest] > log_level=DEBUG > ```...

> > for now , it is only possible to store anything in the file but obtain console output only if test is failing, right? > > Yes that is...