Skip to content
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

unstable test testPrepareSerialSuite.TestPrepareCacheWithJoinTable #25459

Closed
tidb-ci-bot opened this issue Jun 15, 2021 · 1 comment · Fixed by #27335
Closed

unstable test testPrepareSerialSuite.TestPrepareCacheWithJoinTable #25459

tidb-ci-bot opened this issue Jun 15, 2021 · 1 comment · Fixed by #27335
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@tidb-ci-bot
Copy link

Bug Report

prepare_test.go:976:
    ...
/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/util/testleak/leaktest.go:168:
    c.Errorf("Test %s check-count %d appears to have leaked: %v", c.TestName(), cnt, g)
... Error: Test testPrepareSerialSuite.TestPrepareCacheWithJoinTable check-count 50 appears to have leaked: github.com/pingcap/tidb/ddl.(*worker).start(0xc246a90f50, 0xc246ab8180)
	/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/ddl/ddl_worker.go:157 +0x36e
created by github.com/pingcap/tidb/ddl.(*ddl).Start
	/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/ddl/ddl.go:353 +0x6bb

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/676/pipeline/

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master dc40a09

@ti-srebot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants