-
Notifications
You must be signed in to change notification settings - Fork 80
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
TST: Upload to codecov as separate job #2865
Conversation
so it can be re-uploaded separately on upload failure without re-running test suite.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2865 +/- ##
==========================================
- Coverage 88.93% 88.72% -0.22%
==========================================
Files 111 111
Lines 17165 17101 -64
==========================================
- Hits 15266 15173 -93
- Misses 1899 1928 +29 ☔ View full report in Codecov by Sentry. |
This in the log is not our problem:
|
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.
Super useful - looks good to me, thanks!
Co-authored-by: P. L. Lim <[email protected]>
Over at OpenAstronomy/github-actions-workflows#199 , I found a bug in this setup where if we have two jobs that generate coverage, one will clobber the other. Since we only have one coverage job here, it doesn't matter. But if the situation change in the future, we can either switch to OpenAstronomy or I apply the same patch here. FYI. |
so it can be re-uploaded separately on upload failure without re-running test suite.
Description
This pull request is to upload to codecov as separate job so it can be re-uploaded separately on upload failure without re-running test suite.
There is now a new job called
CI / Upload Coverage (pull_request)
in the CI checks. If upload fails, you can just rerun this one instead of the test suite with coverage again.Also see:
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.