-
Notifications
You must be signed in to change notification settings - Fork 287
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
kv/client: fix unstable unit test, where request id is not accurate #1674
Conversation
3e20198
to
60d35b5
Compare
/run-all-tests |
/run-check-release-note |
/lgtm |
/lgtm |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 60d35b5
|
/run-integration-tests |
1 similar comment
/run-integration-tests |
/run-all-tests |
/run-kafka-tests |
1 similar comment
/run-kafka-tests |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #1679 |
What problem does this PR solve?
Fix a test failure in https://github.com/pingcap/ticdc/issues/1501#issuecomment-820027078
Note release-5.0 should be cherry-picked manually.
What is changed and how it works?
The cause is that when the mock TiKV server starts up for the second time, it could cost some time before it is available and kv client will try to request for more than one time.
Check List
Tests
Release note