This repository was archived by the owner on Jul 24, 2024. It is now read-only.
Fix CI failed with "tikv timeout"#481
Merged
ti-srebot merged 2 commits intopingcap:masterfrom Aug 31, 2020
Merged
Conversation
added 2 commits
August 31, 2020 16:37
Signed-off-by: Hillium <maruruku@stu.csust.edu.cn>
Signed-off-by: Hillium <maruruku@stu.csust.edu.cn>
Collaborator
Author
|
/run-integration-test can it resolve the problem stable? |
3pointer
approved these changes
Aug 31, 2020
Collaborator
3pointer
left a comment
There was a problem hiding this comment.
LGTM, we should find which PR bring the fail later
ti-srebot
approved these changes
Aug 31, 2020
Collaborator
Author
|
/merge |
Contributor
|
/run-all-tests |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Signed-off-by: Hillium maruruku@stu.csust.edu.cn
What problem does this PR solve?
Fix CI failed with "tikv timeout"
What is changed and how it works?
Currently, when a lock resolved, the continuing proto message would be incorrect(for unknown reason).
We would get errors like:
After updating
kvproto, the problem seems resolved magically(!).Check List
Tests
Release Note