coverage: workaround for XML reporting bug #857
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There’s a bug in coverage.py when using the source specifier which causes the XML reports to omit the first element of the directory name, breaking some tools (this does not affect the HTML or text format reports). Using include instead avoids this problem until the upstream bug is resolved: nedbat/coveragepy#578
This allows builds to start faster but still has the full history available for code analysis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There’s a bug in coverage.py when using the source specifier which causes the XML reports to omit the first element of the directory name, breaking some tools (this does not affect the HTML or text format reports).
Using include instead avoids this problem until the upstream bug is resolved: nedbat/coveragepy#578
Before merging, we should see a big jump up in the coverage numbers on https://sonarcloud.io/dashboard?id=LibraryOfCongress_concordia because the values in the coverage.xml file will have the full file paths it's looking for.