-
Notifications
You must be signed in to change notification settings - Fork 56
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
Add workflow to upload coverage report on pushes to main #2025
Add workflow to upload coverage report on pushes to main #2025
Conversation
Coverage data that we get from llvm-cov is very noisy and unrelated changes can randomly increase or decrease coverage, failing PR checks. While this behaviour is investigated, blocking coverage-related PR checks are disabled, but reports are still sent. Signed-off-by: Marcel Guzik <marcel.guzik@inetum.com>
Signed-off-by: Marcel Guzik <marcel.guzik@inetum.com>
Robot Results
Passed Tests
|
Codecov Report
Additional details and impacted files
|
While this will probably fix the most obvious unrelated changes, there's still an upstream issue of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine
Proposed changes
Codecov guides suggest uploading coverage for push and pull_request events.
pull-request-checks.yml
only runs on PRs though, and when coverage upload only happens there, it has an effect of codecov patch reports not picking up the latest HEAD and displaying coverage changes that have already been made in previous PRs. To fix this, we upload report every time we push to main, which also happens when a PR gets merged.Also, because coverage data that we get from llvm-cov is somewhat noisy and unrelated changes can randomly increase or decrease coverage, failing PR checks, we disable blocking checks for the time being. Once we tune codecov to a sufficient degree, we can reenable them.
Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments
https://docs.codecov.com/docs/commit-status#informational