unstable test partition_table_test.go:2686: testSuiteWithData.TestRangePartitionBoundariesBetweenS

[zhouqiang-cl]

Bug Report

Please answer these questions before submitting your issue. Thanks!

[2021-06-08T15:06:14.371Z] ----------------------------------------------------------------------
[2021-06-08T15:06:14.371Z] FAIL: partition_table_test.go:2686: testSuiteWithData.TestRangePartitionBoundariesBetweenS
[2021-06-08T15:06:14.371Z] 
[2021-06-08T15:06:14.371Z] partition_table_test.go:2707:
[2021-06-08T15:06:14.371Z]     s.verifyPartitionResult(tk, input, output)
[2021-06-08T15:06:14.371Z] /home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/util/testkit/testkit.go:217:
[2021-06-08T15:06:14.371Z]     tk.c.Assert(err, check.IsNil, check.Commentf("sql:%s, %v, error stack %v", sql, args, errors.ErrorStack(err)))
[2021-06-08T15:06:14.371Z] ... value *errors.fundamental = analyze worker panic ("analyze worker panic")
[2021-06-08T15:06:14.371Z] ... sql:ANALYZE TABLE t, [], error stack analyze worker panic
[2021-06-08T15:06:14.371Z] github.com/pingcap/tidb/executor.init
[2021-06-08T15:06:14.371Z] 	/home/jenkins/agent/workspace/tidb-unit-test-nightly/go/src/github.com/pingcap/tidb/executor/analyze.go:247
[2021-06-08T15:06:14.371Z] runtime.doInit
[2021-06-08T15:06:14.371Z] 	/usr/local/go/src/runtime/proc.go:6309
[2021-06-08T15:06:14.371Z] runtime.doInit
[2021-06-08T15:06:14.371Z] 	/usr/local/go/src/runtime/proc.go:6286
[2021-06-08T15:06:14.371Z] runtime.main
[2021-06-08T15:06:14.371Z] 	/usr/local/go/src/runtime/proc.go:208
[2021-06-08T15:06:14.371Z] runtime.goexit
[2021-06-08T15:06:14.371Z] 	/usr/local/go/src/runtime/asm_amd64.s:1371

1. Minimal reproduce step (Required)

in ci https://ci.pingcap.net/blue/rest/organizations/jenkins/pipelines/tidb-unit-test-nightly/runs/289/nodes/104/steps/350/log/?start=0

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master f81ef55

[mjonss]

This looks like the same issue as #25395. Not the test that is unstable, but a bug in ANALYZE TABLE

[mjonss]

I have tried to reproduce the issue with current master a4146033fb6deec464de9faf5f5412b87ef5d06c without success.
I ran the unit tests in executor directory 100 times with random overlap/concurrent runs. Could it be that there was an issue with ANALYZE TABLE that triggered this unstable test, but has been fixed since this was reported?

[bb7133]

Very likely that it has been fixed by #25547, since the stack looks the same and it doesn't reproduce for several weeks.

Close this issue.

[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