*: upgrade grpcio to v0.3.1, grpcio-sys to v0.3.2 #5441
Merged
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
|
/run-all-tests |
|
/bench |
Signed-off-by: gengliqi <gengliqiii@gmail.com>
gengliqi
force-pushed
the
release-2.1
branch
from
ed6d477
to
a9ecba7
Compare
|
/run-all-tests /bench |
BusyJay
approved these changes
Sep 10, 2019
overvenus
approved these changes
Sep 10, 2019
|
/run-all-tests |
|
@gengliqi merge failed. |
|
/run-test |
|
/test |
|
/run-all-test |
BusyJay
added
status/can-merge
|
/run-all-tests |
Merged
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.
What have you changed?
Upgrade grpcio to v0.3.1, grpcio-sys to v0.3.2 in which fixes a segmentation fault bug in grpc c core.
You can see more details in tikv/grpc#32
What is the type of the changes?
Bugfix
How is the PR tested?
Manual test.
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect
tidb-ansible?No.
Refer to a related PR or issue link (optional)
tikv/grpc-rs#373
tikv/grpc#32