fix:same precision on coverage rates of current and diff branch#49
Merged
cicdguy merged 1 commit intoinsightsengineering:mainfrom Jul 3, 2025
Merged
Conversation
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Minor fix following #47. Addresses the following:
1e-8precision used in the diff branch;tr -d '%'.My bad on the suggestion I left on the PR missing these points 🥲
As an additional note, I thought about adding tests for these edge cases (80% on baseline, 80.000001% / 79.999999% on branches). However, it seems that
pycobertura showcounts line for each<line />element in the xml, so the mock files would require 1e8 lines to do so, which is far from ideal. Due to that, tests were left untouched.