executor: add an unit test case for unreasonable invoking Close (#30696)

[ti-srebot]

cherry-pick #30696 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/30768

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/30768:release-5.0-8cf847a57514

---

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 Close function may be invoked but the Open function is not invoked or returned with an error. In this senario, some member attributes are not initialized and the nil pointer panic triggered when invoking Close.

I add a unit test in this commit to test invoking the Close function directly without invoking the Open function 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

• Unit test

Side effects

N/A

Documentation

N/A

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• guo-shaoge
• wshwsh12

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@XuHuaiyu you're already a collaborator in bot's repo.

[zhouqiang-cl]

/merge

[zhouqiang-cl]

/run-check_dev

[zhouqiang-cl]

/merge

[zhouqiang-cl]

@XuHuaiyu Seems there is an error on ci

[zhouqiang-cl]

[2021-12-19T14:03:39.016Z] level=warning msg="[runner] Can't run linter goanalysis_metalinter: ineffassign: analysis skipped: errors in package: [/home/jenkins/agent/workspace/tidb_ghpr_check/go/src/github.com/pingcap/tidb/executor/executor_test.go:8370:23: PhysicalCTE not declared by package core]"

[2021-12-19T14:03:39.016Z] level=info msg="[runner] processing took 8.239µs with stages: max_same_issues: 4.015µs, skip_dirs: 1.698µs, nolint: 422ns, max_from_linter: 296ns, cgo: 199ns, autogenerated_exclude: 155ns, filename_unadjuster: 143ns, identifier_marker: 141ns, skip_files: 136ns, uniq_by_line: 136ns, severity-rules: 129ns, path_prettifier: 128ns, source_code: 124ns, diff: 124ns, path_shortener: 72ns, exclude: 66ns, max_per_file_from_linter: 64ns, sort_results: 64ns, exclude-rules: 64ns, path_prefixer: 63ns"

[2021-12-19T14:03:39.016Z] level=info msg="[runner] linters took 3.35783262s with stages: goanalysis_metalinter: 3.357741943s"

[2021-12-19T14:03:39.016Z] level=error msg="Running error: ineffassign: analysis skipped: errors in package: [/home/jenkins/agent/workspace/tidb_ghpr_check/go/src/github.com/pingcap/tidb/executor/executor_test.go:8370:23: PhysicalCTE not declared by package core]"

[2021-12-19T14:03:39.016Z] level=info msg="Memory: 72 samples, avg is 403.6MB, max is 878.3MB"

[2021-12-19T14:03:39.016Z] level=info msg="Execution took 7.031901479s"

[2021-12-19T14:03:39.016Z] make: *** [check-static] Error 3

[XuHuaiyu]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 1716233

[XuHuaiyu]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 68ece70

[XuHuaiyu]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 5482ef4

[ti-chi-bot]

@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.

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.