-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
executor: Fix unstable test TestCheckFailReport #31701
executor: Fix unstable test TestCheckFailReport #31701
Conversation
[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 submitting an approval review. |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/038111d41120ecf4be98bf9ed4e532b00caae649 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does fix the bug. But I'm not sure whether it's the most appropriate place to put it.
Please fix build. |
Co-authored-by: Ziqian Qin <ekexium@gmail.com>
@hawkingrei It's not the problem in this PR. |
@hawkingrei PTAL |
What problem does this PR solve?
Issue Number: ref #26833
Problem Summary: TestCheckFailReport is unstable. There's such a problem: when executing admin check, it didn't handle context cancellation correctly, therefore if admin check fails, and another working goroutine inner the TableReaderExecutor returns empty result due to being cancelled, there's some chance that the admin check procedure produced one more false-positive error log, which may cause confusion and misleading.
What is changed and how it works?
After reading from table, exit before reporting error if context is cancelled.
Check List
Tests
Release note