Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a hint that coverage combine might be needed #1781

Open
nedbat opened this issue May 13, 2024 · 0 comments · May be fixed by #1782
Open

Add a hint that coverage combine might be needed #1781

nedbat opened this issue May 13, 2024 · 0 comments · May be fixed by #1782
Labels
enhancement New feature or request

Comments

@nedbat
Copy link
Owner

nedbat commented May 13, 2024

From the Python IRC channel on Libera:

Person: coverage.py's `coverage report` gives me "No data to report.", and it looks like that is because the output file isn't .coverage, but dot-suffixed with my machine name etc. Now, this appears to be done *not* because of `parallel = true` in my config, but because `concurrency = multiprocessing`. However, `coverage report` does not pick up on this, or even when I do explicitly add `parallel = true`
Person: If I specify the output file explicitly when calling `coverage report`, I get the desired output (but that's not a feasible solution as these filenames are not consistent)
Person: fml.... I type out my problem and the solution appears: yes, I have to call `coverage combine` explicitly

The "No data to report" message could check if there are dot-suffixed data files, and add, "Perhaps you need to run coverage combine" or something similar. This would guide people to a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant