-
Notifications
You must be signed in to change notification settings - Fork 365
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
Fix the CodeCov Pipeline #1165
base: master
Are you sure you want to change the base?
Fix the CodeCov Pipeline #1165
Conversation
28578ea
to
be59569
Compare
8ffce2e
to
676caa0
Compare
94269a5
to
1c7a168
Compare
4fba69b
to
c7c5bdb
Compare
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.
LGTM
9d26498
to
c49b588
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1165 +/- ##
==========================================
- Coverage 74.81% 65.96% -8.85%
==========================================
Files 144 143 -1
Lines 16248 16188 -60
==========================================
- Hits 12156 10679 -1477
- Misses 3152 4756 +1604
+ Partials 940 753 -187 ☔ View full report in Codecov by Sentry. |
5405e77
to
5a2046d
Compare
Update the ci to go version 20, fix go test coveroutput and add listener that terminates the api in testing mode.
5a2046d
to
c8ea704
Compare
The code coverage has had some issues in the past, which are addressed by this change.
Fixes: #1164
Requirements
All new code should be covered with tests, documentation should be updated. CI should pass.
Description of the Change
I changed the
go test
command to output to the GOCOVERDIR and upgraded the ci to go version1.20
.I also had to fix some issues that the linter detected, mainly replacing unused parameters with
_
.Why this change is important?
The coverage should be accurate and it's not bad to test on the latest go version either.
Checklist
AUTHORS