Leak test in TestPrepareTableAsNameOnGroupByWithCache

[zhouqiang-cl]

Bug Report

[2021-06-14T12:17:45.562Z] FAIL: prepare_test.go:304: testPrepareSerialSuite.TestPrepareTableAsNameOnGroupByWithCache

[2021-06-14T12:17:45.562Z] 

[2021-06-14T12:17:45.562Z] prepare_test.go:343:

[2021-06-14T12:17:45.562Z]     ...

[2021-06-14T12:17:45.562Z] /home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/util/testleak/leaktest.go:168:

[2021-06-14T12:17:45.562Z]     c.Errorf("Test %s check-count %d appears to have leaked: %v", c.TestName(), cnt, g)

[2021-06-14T12:17:45.562Z] ... Error: Test testPrepareSerialSuite.TestPrepareTableAsNameOnGroupByWithCache check-count 50 appears to have leaked: github.com/pingcap/tidb/domain.(*Domain).globalBindHandleWorkerLoop.func1(0xc31d4214a0)

[2021-06-14T12:17:45.562Z] 	/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/domain/domain.go:1005 +0x12a

[2021-06-14T12:17:45.562Z] created by github.com/pingcap/tidb/domain.(*Domain).globalBindHandleWorkerLoop

[2021-06-14T12:17:45.562Z] 	/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/domain/domain.go:996 +0x5f

[2021-06-14T12:17:45.562Z] 

[2021-06-14T12:17:45.562Z] OOPS: 363 passed, 1 FAILED

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

in ci https://ci.pingcap.net/blue/organizations/jenkins/tidb-unit-test-nightly/detail/tidb-unit-test-nightly/644/pipeline

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master a45b3aa

[qw4990]

Seems to be fixed by #26500. I'll close it now, if it appears again, please reopen it.

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions