-
-
Notifications
You must be signed in to change notification settings - Fork 349
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
Bump Codecov action to v5 #3161
base: main
Are you sure you want to change the base?
Conversation
a4c4838
to
e2b6bb6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3161 +/- ##
=====================================================
- Coverage 100.00000% 55.50685% -44.49315%
=====================================================
Files 124 246 +122
Lines 18460 37644 +19184
Branches 1216 2727 +1511
=====================================================
+ Hits 18460 20895 +2435
- Misses 0 16426 +16426
- Partials 0 323 +323 |
#2951 should have some prior research |
Yeah, that also surprised me. It does need research… One should probably start by comparing the payloads between the PR and main.. |
@webknjaz I think you've not enabled edits from maintainers, so I can't update this branch from the base branch for you |
Yeah, I often disable that. |
e2b6bb6
to
1290249
Compare
Anyway, with the huge reported coverage drop and the flakiness I was observing in Ansible, I'd like to investigate what's broken in Codecov first. |
# `nodejs` for pyright (`node-env` pulls in nodejs but that takes a while and can time out the test). | ||
# `perl` for a platform independent `sed -i` alternative | ||
run: apk update && apk add python3-dev bash nodejs perl | ||
run: apk update && apk add python3-dev bash curl gpg git jq nodejs perl |
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.
fyi, jq
should no longer be needed. I'm working on gpg
and git
, though git
is probably still recommended
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.
That's too bad. The best practice is to build and test from sdist, meaning that there would be no Git repo on disk.
It's more stable and requires a token that is already in the config. Alpine needs curl, gpg, git and jq because of a bug in codecov-action [[1]]. [1]: codecov/codecov-action#1320
1290249
to
b2862a4
Compare
It's more stable and requires a token that is already in the config.