-
Notifications
You must be signed in to change notification settings - Fork 672
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 uploading of code coverage data #5298
Conversation
Signed-off-by: Eduardo Apolinario <[email protected]>
#5294 is upgrading the version of the gh actions used to checkout the repo. While this is good we should address this failure at a lower level (which is being done in the present PR). |
Signed-off-by: Eduardo Apolinario <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5298 +/- ##
==========================================
+ Coverage 59.02% 60.19% +1.16%
==========================================
Files 383 646 +263
Lines 29801 45654 +15853
==========================================
+ Hits 17590 27480 +9890
- Misses 10485 15582 +5097
- Partials 1726 2592 +866
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
* Do not upload codecoverage data from boilerplate Signed-off-by: Eduardo Apolinario <[email protected]> * Use correct token to upload code coverage data Signed-off-by: Eduardo Apolinario <[email protected]> * Pipe in CODECOV_TOKEN as an input secret Signed-off-by: Eduardo Apolinario <[email protected]> * Actually pipe the secret in Signed-off-by: Eduardo Apolinario <[email protected]> * Pipe codecov token in flyteidl tests too --------- Signed-off-by: Eduardo Apolinario <[email protected]> Co-authored-by: Eduardo Apolinario <[email protected]>
Why are the changes needed?
The ingestion of code coverage data was happening in two places:
test_unit_codecov
make target defined in boilerplateAs of a few days ago we started seeing the upload done in 1. timeout and block the execution of the remaining steps in the gh workflow, e.g. [1].
That said, 2. was never configured properly. For example, we were reusing the
flags
field, which essentially caused the code coverage data to be overwritten. Another problem was that we never used the correct name for the token.What changes were proposed in this pull request?
Three changes:
flags
field such that the code coverage data can be aggregated correctlytoken
field with a proper value to upload codecov data via the gh action.How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link