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

Some partition tests are non stable #33059

Closed
morgo opened this issue Mar 14, 2022 · 0 comments · Fixed by #33060
Closed

Some partition tests are non stable #33059

morgo opened this issue Mar 14, 2022 · 0 comments · Fixed by #33060
Labels
affects-6.0 component/test feature/developing the related feature is in development severity/major type/bug The issue is confirmed as a bug.

Comments

@morgo
Copy link
Contributor

morgo commented Mar 14, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

go test

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

no error

3. What did you see instead (Required)

--- FAIL: TestFourReader (0.10s)
    result.go:50: 
                Error Trace:    result.go:50
                                                        partition_table_test.go:61
                Error:          Not equal: 
                                expected: "[0]\n[9]\n"
                                actual  : "[9]\n[0]\n"
                                
                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1,3 +1,3 @@
                                +[9]
                                 [0]
                                -[9]
                                 
                Test:           TestFourReader
                Messages:       sql:select c from pt where c < 2 or c >= 9, args:[]


--- FAIL: TestGlobalIndexDoubleRead (0.13s)
    result.go:50: 
                Error Trace:    result.go:50
                                                        partition_table_test.go:2848
                Error:          Not equal: 
                                expected: "[1 3]\n[3 4]\n[5 6]\n[7 9]\n"
                                actual  : "[3 4]\n[5 6]\n[7 9]\n[1 3]\n"
                                
                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1,2 +1 @@
                                -[1 3]
                                 [3 4]
                                @@ -4,2 +3,3 @@
                                 [7 9]
                                +[1 3]
                                 
                Test:           TestGlobalIndexDoubleRead
                Messages:       sql:select * from p use index (idx), args:[]

4. What is your TiDB version? (Required)

master

@morgo morgo added the type/bug The issue is confirmed as a bug. label Mar 14, 2022
@morgo morgo added the feature/developing the related feature is in development label Mar 14, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. labels Mar 15, 2022
@ChenPeng2013 ChenPeng2013 removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. labels Mar 15, 2022
ti-chi-bot pushed a commit that referenced this issue Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.0 component/test feature/developing the related feature is in development severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants