-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Manually merge 2.10.x into 2.11.x #4186
Conversation
CI platforms do not run their jobs on the commit you push. Instead, they run it on a merge commit so that both your changes and the latest version of the target branch are taken into account. Before uploading the coverage report, CodeCov's bash uploader attempts to find the original commit hash, and succeeds on Travis and AppVeyor, but not on Github, because the method it uses does not work unless the parent commits are fetched too, which results in Github posting to CodeCov with a different hash than Travis or AppVeyor. Setting the fetch depth fixes that issue.
Fetch parent commits
A merge is viewed by Github as a push to the branch where the merge occurs, see https://github.uint.cloudmunity/t/trigger-workflow-only-on-pull-request-merge/17359/2 This means we should have coverage reports for merge commits from Github, which should result in saner numbers.
Trigger Github workflow for merges
@greg0ire this assumes that you finished working on the code coverage fixes in |
Let me just rebase #4180 |
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.
I have to go, approving in case the results of #4180 look ok to you
This time, the coverage of a couple of OCI8-related classes dropped. Supposedly this is what integration tests would cover. Looks legit. |
…tors Ignore code coverage of private constructors of static classes
On top of the changes from
2.10.x
, contains the removal of the handling of the obsolete performance test group.