-
-
Notifications
You must be signed in to change notification settings - Fork 426
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
Paper cut: Better handling of "CoverageException: Can't add arcs to existing line data" ? #803
Labels
enhancement
New feature or request
Milestone
Comments
I think you are right, this is definitely a place where the messaging could be made more relevant to the user's perspective rather than the code's perspective, so that the user understands what's happening. |
This is now released as part of coverage 5.5. |
This was referenced Mar 12, 2021
This was referenced May 21, 2021
1 task
This was referenced Jun 6, 2021
This was referenced Jun 6, 2021
1 task
This was referenced Jul 15, 2021
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Previous closed issue, with comments: #476
Reproduction: In the process of adding coverage to an existing project's test suite, I first ran it without branch coverage, and then again after enabling branch coverage in
.coveragerc
, resulting in "CoverageException: Can't add arcs to existing line data".I'm familiar enough with coverage to have guessed that it's a data file format problem, and deleted the
.coverage
file to fix it, but this won't be obvious to new or inexperienced users, and it probably represents a significant usability hurdle / paper cut bug (especially since it's most likely to occur when first adding coverage to a project in this way)Describe the solution you'd like
One or more of:
Additional context
This is the relevant traceback (with coverage 4.5.3, invoked via
nosetests --with-coverage
):The text was updated successfully, but these errors were encountered: