ci: merge coverage with regular CI tests #116
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We have the separate because we run the tests on multiple platforms and multiple python versions, but we only want to run coverage reports on one platform and one python version. This is the standard pattern on most Scientific Python projects. |
I see, but with Codecov, id does a fusion of all received reports for a particular commit, and with the newly added flags/tags, you can validate what lines are visited only for a specific configuration... Anyway, just a suggestion, and feel free to close it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This could simplify maintenance as the testing and reporting coverage workflows are almost the same, so let's add reporting coverage to the main one and drop the additional/duplicate...