-
-
Notifications
You must be signed in to change notification settings - Fork 445
annotate command fails to annotate many files #57
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
Comments
Original comment by smontanaro (Bitbucket: smontanaro, GitHub: smontanaro) I figured out what was preventing annotation. In AnnotateReport.annotate_file it I'm not sure what the ultimate solution is, but simply considering files absolute |
Original comment by Anonymous I just hit a similar issue with the same solution. Not sure why annotate depends on the code unit being a relative path?? annotate.annotate_file: line 50 coverage version, 3.4 Please note, I experienced this by using the API calls directly for annotate and html output:
Same calls, same data, annotate returns nothing and html returns it all. |
Fixed in 121d6cab4bf7 (bb) |
Issue #321 was marked as a duplicate of this issue. |
Originally reported by smontanaro (Bitbucket: smontanaro, GitHub: smontanaro)
I just upgraded to the latest version of the coverage module. We have
a reasonably complex installation of internal Python modules at work.
I made a long test run overnight and this morning asked for a coverage
report. It looked fine:
Then I asked it to generate annotated listings:
Looking in my cover directory I only saw one file:
How do I get it to generate coverage output for the other 240+ modules?
The text was updated successfully, but these errors were encountered: