Skip to content

ci: fix coverage report validation and rounding - #259

Open
kralicky wants to merge 1 commit into
mainfrom
kralicky/coverage-report-fixes
Open

ci: fix coverage report validation and rounding#259
kralicky wants to merge 1 commit into
mainfrom
kralicky/coverage-report-fixes

Conversation

@kralicky

Copy link
Copy Markdown
Collaborator

Fixes a few issues related to coverage reports:

  • Use our own coverage.yaml instead of the default upstream one
  • Fix coverage % rounding. The upstream behavior appears to be to round to 1 decimal place, but this is undesirable if the threshold is 100%.
  • Re-enable branch coverage
  • In CI, log the coverage report summary text and fail the workflow if the threshold is not reached.

@kralicky
kralicky requested a review from kenjenkins July 20, 2026 23:34
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 29787621667

Warning

No base build found for commit a949754 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 100.0%

Details

  • Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 7770
Covered Lines: 7770
Line Coverage: 100.0%
Relevant Branches: 4500
Covered Branches: 3434
Branch Coverage: 76.31%
Branches in Coverage %: No
Coverage Strength: 20141.7 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants