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 testSerialSuite.TestTiDBLastTxnInfoCommitMode #25121

Closed
zhouqiang-cl opened this issue Jun 4, 2021 · 3 comments
Closed

unstable test testSerialSuite.TestTiDBLastTxnInfoCommitMode #25121

zhouqiang-cl opened this issue Jun 4, 2021 · 3 comments
Assignees
Labels
severity/major type/bug This issue is a bug.

Comments

@zhouqiang-cl
Copy link
Contributor

Bug Report

[2021-06-03T16:39:02.989Z] 
[2021-06-03T16:39:02.989Z] ----------------------------------------------------------------------
[2021-06-03T16:39:02.989Z] FAIL: executor_test.go:3022: testSerialSuite.TestTiDBLastTxnInfoCommitMode
[2021-06-03T16:39:02.989Z] 
[2021-06-03T16:39:02.989Z] [["async_commit" false false]]
[2021-06-03T16:39:02.989Z] [["async_commit" false false]]
[2021-06-03T16:39:02.989Z] executor_test.go:3068:
[2021-06-03T16:39:02.989Z]     c.Assert(rows[0][0], Equals, `"2pc"`)
[2021-06-03T16:39:02.989Z] ... obtained string = "\"async_commit\""
[2021-06-03T16:39:02.989Z] ... expected string = "\"2pc\""

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/87/pipeline/18

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

releasse-5.0 0ecd6bd

@bb7133
Copy link
Member

bb7133 commented Jun 4, 2021

This issue expects the backport of #24779.

/cc @MyonKeminta

@MyonKeminta
Copy link
Contributor

The cherrypick to 5.0 was merged

@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 type/bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

4 participants