Ned Batchelder
Ned Batchelder
I understand that impulse. We would like to keep our plugin as simple as possible.
@bcbnz The note about adding "pass" being too broad is a good one, I will add that to the coverage.py docs. There's something people are missing in this discussion: since...
In the first case, you are getting a warning that no data was collected. pytest finds no code to run, so it never executes src/tmp.py. You can verify this with:...
It turns out bug 915 wasn't because of the double-nesting of coverage, but it could still be a good idea to disallow it somehow.
Another option is to simply use the `coverage report` command instead of having pytest-cov do the reporting. There's no need for the reporting to happen in the pytest plugin.
How are you running pytest under tox? Both pytest and coverage are installed in your environment, and both are runnable as either commands or as Python modules. Maybe I'm missing...
This will be a problem due to coverage.py and its interactions with PyTorch. I thought there was an issue already about it, but I don't see it now. Feel free...
Thanks. Can you provide details about how you configure your virtualenv and run your tests?
If you are seeing this issue, can you increase the reporting precision to see what the actual coverage value is? For example, if the total coverage is 93.18757, it will...
@revesansparole I'm curious: why don't you want the coverage measurement when you run tests inside pycharm?