Ned Batchelder

The docs have this: ```rst .. note:: The subprocess only sees options in the configuration file. Options set on the command line will not be used in the subprocesses. ```...

It's hard for me to see how multiprocessing could interfere with in-process measurement of coroutines. Can you provide use with a reproducible demonstration of the problem.

I notice that your pip freeze output doesn't mention "coverage"? Are you sure you are using the same version? You mention 6.5.0, but perhaps it is different in the working...

Do you have any more information about how I might be able to reproduce this? Can you link us to the repo with the code?

> I have checked the plugin starting the subprocess, (pytest-flask, file live_server.py) and it sends a SIGINT to the process before calling the join (which seems to be aligned with...

Check if the server is started with `debug=True`: that can run your code inside a debugger, which interferes with coverage.py data collection. See #1663.

I don't see the errors you mention: ``` % python -m tox --parallel auto ⠙ [6/6] py38-more_itertools812 | py38-more_itertools813 | py38-more_itertools814 | py39-more_itertools812 |.../usr/local/virtualenvs/tmp-46d8ab1a6519ed3/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use...

If this is still a problem for you, can you try adding this line to your coverage configuration? ``` [run] data_file = .coverage-${TOX_ENV_NAME} ```

It works a little better like this: ```ini [run] data_file = .coverage.${TOX_ENV_NAME} ``` (dot instead of dash) Then each tox environment produces its own file without conflict. You can then...

> That's a bit different - I'd welcome your thoughts on some of the differences, including: > > - using {envname} instead of ${TOX_ENV_NAME} > - using setenv COVERAGE_FILE within...