executor: add an unit test case for unreasonable invoking Close (#30696)#30769
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
[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. |
|
/run-all-tests |
|
@XuHuaiyu you're already a collaborator in bot's repo. |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 22061c6 |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: e0b6270 |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a30d028 |
cherry-pick #30696 to release-5.1
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/30769After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
Inspired by #27125, #30587, and #30289, there is a common problem that the
Closefunction may be invoked but theOpenfunction is not invoked or returned with an error. In this senario, some member attributes are not initialized and the nil pointer panic triggered when invokingClose.I add a unit test in this commit to test invoking the
Closefunction directly without invoking theOpenfunction before.With this test, 3 more similar bugs are also found in
MergeJoinExec,CTEExec,IndexReader.What is changed and how it works?
Check List
Tests
Side effects
N/A
Documentation
N/A
Release note