executor: Fix unstable TestTiDBLastTxnInfoCommitMode (#24779)#25160
executor: Fix unstable TestTiDBLastTxnInfoCommitMode (#24779)#25160ti-chi-bot merged 3 commits intopingcap:release-5.0from
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
/run-all-tests |
|
@MyonKeminta you're already a collaborator in bot's repo. |
|
@cfzjywxk: Please use GitHub review feature instead of For the reason we drop support to the commands, see also this page. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
[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. DetailsReviewer can indicate their review by submitting an approval review. |
|
/merge |
|
@bb7133: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a94f072 |
|
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
cherry-pick #24779 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/25160After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #24774
Problem Summary:
The test case
TestTiDBLastTxnInfoCommitModeis unstable, because in the case it assumes whenAsyncCommit.SafeWindow = 0the async commit / 1pc will surely fallback, which is incorrect.What is changed and how it works?
What's Changed:
Use the failpoint
invalidMaxCommitTSinstead of settingSafeWindow = 0to trigger falling back.Related changes
Check List
Tests
Side effects
Release note