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

test: random "IsolationRead" fails in testAnalyzeSuite.TestIndexRead #14579

Closed
bb7133 opened this issue Jan 28, 2020 · 1 comment · Fixed by #14615
Closed

test: random "IsolationRead" fails in testAnalyzeSuite.TestIndexRead #14579

bb7133 opened this issue Jan 28, 2020 · 1 comment · Fixed by #14615
Assignees
Labels
component/test severity/minor type/bug The issue is confirmed as a bug.

Comments

@bb7133
Copy link
Member

bb7133 commented Jan 28, 2020

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
[2020-01-28T06:41:04.848Z] FAIL: cbo_test.go:236: testAnalyzeSuite.TestIndexRead
[2020-01-28T06:41:04.848Z] 
[2020-01-28T06:41:04.848Z] cbo_test.go:276:
[2020-01-28T06:41:04.848Z]     c.Assert(err, IsNil)
[2020-01-28T06:41:04.848Z] ... value *errors.withStack = [planner:1815]Internal : Can not find access path matching 'tidb_isolation_read_engines'(value: '[tiflash]') and tidb-server config isolation-read(engines: 'tikv,tiflash,tidb'). Available values are 'tikv'. ("[planner:1815]Internal : Can not find access path matching 'tidb_isolation_read_engines'(value: '[tiflash]') and tidb-server config isolation-read(engines: 'tikv,tiflash,tidb'). Available values are 'tikv'.")

The error is shown in https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/tidb_ghpr_check_2/detail/tidb_ghpr_check_2/22700/pipeline/

@bb7133 bb7133 added type/bug The issue is confirmed as a bug. component/test labels Jan 28, 2020
@bb7133
Copy link
Member Author

bb7133 commented Jan 28, 2020

PTAL @lzmhhh123 , thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/test severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants