Open RockBomber opened 7 years ago
this is a bug in the configuration initialization of pytest core, its incredibly hard to fix and related to #1618
Having this issue as well, but the referenced ticket won't load for me. You mention it's "incredibly hard to fix", are there any other resources that may help me address it?
oh, github broke on that one :-1:
the first step is to remove the required flag for the argument and check in a pytest-configure hook its a crude hack but works
a "good" fix needs larger refactoring in both pytest and xdist, i didnt even find time to investigate the exact needs yet
Awesome, thanks. I pass environment in as a required argument, and I don't like using a default as the user could potentially think they're testing something they're not.
use none as the default and fail in pytest_configure
with a pytest.UsageError
Is there any fix for this the bug? I have same problem. My platform : linux -- Python 3.5.2, pytest-3.5.0, py-1.5.3, pluggy-0.6.0 plugins: xdist-1.22.2, forked-0.2
@ultinous-meli2200 no there isnt, please use the mentioned workaround
Hi All!
I have a simple test with custom required argument option:
When I run tests in single process mode, I have no errors. But when I run tests in parallelization mode with xdist, I've got infinity errors: