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 analyze_test.go:577: testSuite1.TestAnalyzeIncremental #25010

Closed
Tracked by #25899
zhouqiang-cl opened this issue Jun 1, 2021 · 2 comments
Closed
Tracked by #25899
Assignees
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@zhouqiang-cl
Copy link
Contributor

zhouqiang-cl commented Jun 1, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

[2021-05-31T16:06:57.994Z] [2021/06/01 00:06:57.805 +08:00] [INFO] [session.go:2722] ["CRUCIAL OPERATION"] [conn=118] [schemaVersion=68] [cur_db=test] [sql="CREATE TABLE test_gc_read_cast(a VARCHAR(255), b VARCHAR(255), c INT AS (JSON_EXTRACT(a, b)), d INT AS (JSON_EXTRACT(a, b)) STORED)"] [user=]
[2021-05-31T16:06:57.994Z] 
[2021-05-31T16:06:57.994Z] ----------------------------------------------------------------------
[2021-05-31T16:06:57.994Z] FAIL: analyze_test.go:577: testSuite1.TestAnalyzeIncremental
[2021-05-31T16:06:57.994Z] 
[2021-05-31T16:06:57.994Z] analyze_test.go:581:
[2021-05-31T16:06:57.994Z]     s.testAnalyzeIncremental(tk, c)
[2021-05-31T16:06:57.994Z] /home/jenkins/agent/workspace/tidb_ghpr_unit_test/go/src/github.com/pingcap/tidb/util/testkit/testkit.go:63:
[2021-05-31T16:06:57.994Z]     res.c.Assert(resBuff.String(), check.Equals, needBuff.String(), res.comment)
[2021-05-31T16:06:57.994Z] ... obtained string = "" +
[2021-05-31T16:06:57.994Z] ...     "[test t  a 0 0 1 1 1 1 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  a 0 1 2 1 2 2 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  idx 1 0 1 1 1 1 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  idx 1 1 2 1 2 2 0]\n"
[2021-05-31T16:06:57.994Z] ... expected string = "" +
[2021-05-31T16:06:57.994Z] ...     "[test t  a 0 0 1 1 1 1 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  a 0 1 3 0 2 2147483647 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  idx 1 0 1 1 1 1 0]\n" +
[2021-05-31T16:06:57.994Z] ...     "[test t  idx 1 1 2 1 2 2 0]\n"
[2021-05-31T16:06:57.994Z] ... sql:show stats_buckets, args:[]
[2021-05-31T16:06:57.994Z] 
[2021-05-31T16:06:57.994Z] [2021/06/01 00:06:57.812 +08:00] [INFO] [ddl_worker.go:682] ["[ddl] run DDL job"] [worker="worker 45, tp general"] [job="ID:134, Type:drop table, State:none, SchemaState:queueing, SchemaID:1, TableID:132, RowCount:0, ArgLen:0, start time: 2021-06-01 00:06:57.785 +0800 CST, Err:<nil>, ErrCount:0, SnapshotVersion:0"]
[2021-05-31T16:06:57.994Z] 
[2021-05-31T16:06:57.994Z] ----------------------------------------------------------------------

1. Minimal reproduce step (Required)

in ci https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/4131/pipeline/19

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

matter: a80047c

@qw4990
Copy link
Contributor

qw4990 commented Jul 26, 2021

Solved by #26468

@qw4990 qw4990 closed this as completed Jul 26, 2021
@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

No branches or pull requests

6 participants