Where do these .coverage.hostname.number.number files come from? about pytest-cov HOT 16 CLOSED

They appear if you use subprocesses or xdist.

from pytest-cov.

They don't get removed at the end of the testrun?!

from pytest-cov.

Ah, that's a useful bit of information. Yes, I use subprocess and on error, I sys.exit() so they probably cannot be cleaned up. Do you have an idea? Here is the code inside setup.py.

from pytest-cov.

I mean, if you use subprocesses in your tests, then pytest-cov will automatically start measuring coverage in those processes (if they are python of course). That's what is making those files (besides using xdist).

from pytest-cov.

Oh, I don't use subprocess in my tests, just in my setup.py to run pytest.

from pytest-cov.

Does it reproduce without the setup.py shim?

from pytest-cov.

Just tried that. The files are still created when I just run python -m pytest --cov=layered test or py.test --cov=layered test. Pytest version 2.8.5 and Pytest-cov version 2.2.0.

from pytest-cov.

What's your coverage version?

from pytest-cov.

Coverage is version 4.0.3. Pip says all of the three packages are up-to-date. Update: I just noticed messages of this form in the Pytest report:

Coverage.py warning: Couldn't read data from '/home/danijar/repository/layered/.coverage.danijar-xps13-arch.22012.752324': CoverageException: Doesn't seem to be a coverage.py data file

from pytest-cov.

Is there a repository that reproduce the issue?

from pytest-cov.

Yes, cloning danijar/layered and running python3 setup.py test reproduces the problem.

from pytest-cov.

Have the same issue when using asyncio with ProcessPoolExecutor.

At the testing, it is a lot of .coveage.<..> files, but 2 of them always not get removed after tests complete.

python 3.5.3, coverage==4.4.1 pytest==3.0.6 pytest-cov==2.5.1

from pytest-cov.

So I've looked at @danijar code and I bet @iAnanich has the same problem: unclean multiprocessing pool shutdown. You should have a pool.join() or similar before the test using the pool is done.

from pytest-cov.

Thanks for looking into this!

from pytest-cov.

I have a similar issue when testing a piece of code which uses GridSearchCV. Under the hood, joblib.Parallel is used and I guess/understand that it somehow messes up the files generated.

Any idea how to resolve this issue?

from pytest-cov.

@danijar pls open up a separate issue and give some details.

from pytest-cov.