planner: stabilize tests in binary_plan_test.go

[time-and-fate]

What problem does this PR solve?

Issue Number: close #40004 close #41297

Problem Summary:

Try to fix the above two unstable test cases.

What is changed and how it works?

1. TestTooLongBinaryPlan: I'm unable to reproduce this fail. But I suspect this is because this case is affected by other cases. So I disable and then enable stmt summary in this case to trigger clear the stmt summary in memory, hoping this can fix the problem.
2. TestLongBinaryPlan: I added a rather strict check when I wrote this test case. It looks like this is too strict and even small changes might break this case. So I removed some non-necessary checks.
3. I also reset the global variables in the test cases of this file to reduce the possibility of test cases affecting each other.
4. As @hawkingrei advised, update timeout of planner/core to "short".

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hawkingrei
• qw4990

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.

[time-and-fate]

/test ?

[ti-chi-bot]

@time-and-fate: The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

Use /test all to run all jobs.

In response to this:

/test ?

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 kubernetes/test-infra repository.

[time-and-fate]

/check-issue-triage-complete

[time-and-fate]

/merge

[ti-chi-bot]

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

Commit hash: c4b9292