Open andras-tim opened 6 years ago
The plugin does not do anything to make this be the case... Are you sure this is due to the pytest-flake8 plugin? It does not happen with other plugins (or the base of pytest)? Does it happen if you run pytest directly (and not with tox)?
@tholo, I'm going to check something for I can provide more details. I have an idea about it can be a pytest bug instead of pytest-flake8 (e.g. a masked or badly propagated signal)
In other hands, why I get this lof of debug messages into the captured log when I enable pytest-flake8 plugin?
Because you have one or more flake8 “failures”, which causes pytest to output any and all captured log output during the failed “test”; this is new behavior in pytest...
Thorsten
On Dec 7, 2017, at 14:26, Andras Tim notifications@github.com wrote:
@tholo, I'm going to check something for I can provide more details. I have an idea about it can be a pytest bug instead of pytest-flake8 (e.g. a masked or badly propagated signal)
In other hands, why I get this lof of debug messages into the captured log when I enable pytest-flake8 plugin?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I regurarly use
pytest-flake8
, but now I can't terminate the flake8 check with Ctrl+C, because the main thread is exited, but the tests still running.I think, this is off-topic, but there are a lot of Captured log too: