-
Notifications
You must be signed in to change notification settings - Fork 45
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 C++ coverage in CI and upload all coverage reports to CodeCov #86
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #86 +/- ##
=======================================
Coverage ? 82.48%
=======================================
Files ? 27
Lines ? 3260
Branches ? 226
=======================================
Hits ? 2689
Misses ? 571
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The only thing the "build" workflow is used for is coverage testing. Signed-off-by: Matt Wozniski <mwozniski@bloomberg.net>
Signed-off-by: Gus Monod <gmonod1@bloomberg.net>
Put them all in a single file and publish a report for both of them. Signed-off-by: Gus Monod <gmonod1@bloomberg.net>
Now that the Cython code is also counted, we have a few more lines and branches that aren't covered. This change makes it so that CI passes even though, once we include the Cython code, the coverage is about 96% instead of 100% as it was earlier. Signed-off-by: Gus Monod <gmonod1@bloomberg.net>
Signed-off-by: Gus Monod <gmonod1@bloomberg.net>
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
Issue number of the reported bug or feature request: #62
Describe your changes
This change will calculate the C++, Cython and Python coverage in CI, and upload the results to CodeCov. CodeCov then provides a PR hook to let you know if and how coverage has changed for any of these three.
Testing performed
I tested on a personal fork of the project, and have set-up the appropriate secrets for the official Bloomberg fork already. If everything goes well, this PR should be the only one necessary, and I feel more confident that it will now that I was able to test it on my own fork.
Additional context
See examples of what this would look like here:
Example PR causing coverage reduction: https://github.com/gusmonod/pystack/pull/11
Example PR causing no coverage reduction: https://github.com/gusmonod/pystack/pull/12