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 TestOrderByAndLimit #45496

Closed
Tracked by #41316
hawkingrei opened this issue Jul 21, 2023 · 0 comments · Fixed by #45513
Closed
Tracked by #41316

unstable test TestOrderByAndLimit #45496

hawkingrei opened this issue Jul 21, 2023 · 0 comments · Fixed by #45513
Assignees
Labels
component/test severity/moderate type/bug The issue is confirmed as a bug.

Comments

@hawkingrei
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

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

3. What did you see instead (Required)

     result.go:49: 
        	Error Trace:	testkit/result.go:49
        	            				executor/partition_table_test.go:602
        	Error:      	Not equal: 
        	            	expected: "[1025 1127]\n"
        	            	actual  : "[534 1127]\n"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1,2 +1,2 @@
        	            	-[1025 1127]
        	            	+[534 1127]
        	            	 
        	Test:       	TestOrderByAndLimit
        	Messages:   	sql:select /*+ LIMIT_TO_COP() */ * from tlist use index(idx_b) where b > 1126 and b < greatest(1127+1, 1127) order by b limit 1, args:[] 

https://tiprow.hawkingrei.com/view/gs/pingcapprow/pr-logs/pull/pingcap_tidb/45493/tiprow_fast_test/1682257303933292544

4. What is your TiDB version? (Required)

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

Successfully merging a pull request may close this issue.

2 participants