coverage erase doesn't remove files generated by parallel/concurrency

Issue #635 closed
Former user created an issue


When running coverage erase, I would expect it cleans .coverage.xx.yy files generated by the previous multithreaded run.

However, on a pure implementation point of view, it might be better to not make it a default, but add a --parallel option to the cleancommand instead.

Comments (2)

  1. Jonathan Huot

    (owner of the issue above)

    Note that the workaround is simple:

    coverage combine || true
    coverage erase

    However it makes things a bit odd, e.g. before I fully understood that coverage erase was not erasing my files, I published multiples times wrong reports.

  2. Log in to comment