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

flaky test TestAddPartitionReplicaBiggerThanTiFlashStores #56237

Closed
Tracked by #41316
hawkingrei opened this issue Sep 23, 2024 · 5 comments
Closed
Tracked by #41316

flaky test TestAddPartitionReplicaBiggerThanTiFlashStores #56237

hawkingrei opened this issue Sep 23, 2024 · 5 comments
Labels
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)

     db_partition_test.go:2798: 
        	Error Trace:	pkg/ddl/tests/partition/db_partition_test.go:2798
        	Error:      	Not equal: 
        	            	expected: "[ddl:-1]DDL job rollback, error msg: [ddl] add partition wait for tiflash replica to complete"
        	            	actual  : "[ddl:-1]panic in handling DDL logic and error count beyond the limitation 3, cancelled"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-[ddl:-1]DDL job rollback, error msg: [ddl] add partition wait for tiflash replica to complete
        	            	+[ddl:-1]panic in handling DDL logic and error count beyond the limitation 3, cancelled
        	Test:       	TestAddPartitionReplicaBiggerThanTiFlashStores 

4. What is your TiDB version? (Required)

@hawkingrei hawkingrei added the type/bug The issue is confirmed as a bug. label Sep 23, 2024
@joechenrh
Copy link
Contributor

Maybe fixed by #56222 ?

@hawkingrei
Copy link
Member Author

Maybe fixed by #56222 ?

If you are sufficiently certain, you may help me close this issue.

@joechenrh
Copy link
Contributor

I can't close the issue? 🤔

@hawkingrei
Copy link
Member Author

I close the issue first. if I find this problem again, i will reopen it.

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

No branches or pull requests

2 participants