Skip to content
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

Merged
merged 11 commits into from
Jul 23, 2020
Merged

Manually merge 2.10.x into 2.11.x #4186

merged 11 commits into from
Jul 23, 2020

Conversation

morozov
Copy link
Member

@morozov morozov commented Jul 23, 2020

On top of the changes from 2.10.x, contains the removal of the handling of the obsolete performance test group.

greg0ire and others added 8 commits July 22, 2020 21:14
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.
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.
@morozov
Copy link
Member Author

morozov commented Jul 23, 2020

@greg0ire this assumes that you finished working on the code coverage fixes in 2.10.x. Otherwise, the merge up can wait.

@morozov morozov requested a review from greg0ire July 23, 2020 16:08
@greg0ire
Copy link
Member

Let me just rebase #4180

greg0ire
greg0ire previously approved these changes Jul 23, 2020
Copy link
Member

@greg0ire greg0ire left a 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

@morozov
Copy link
Member Author

morozov commented Jul 23, 2020

[…] 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.

@morozov morozov marked this pull request as draft July 23, 2020 19:33
@morozov morozov requested a review from greg0ire July 23, 2020 20:12
@morozov morozov merged commit b9985b5 into doctrine:2.11.x Jul 23, 2020
@morozov morozov self-assigned this Jul 23, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants