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 TestMemTracker4InsertAndReplaceExec #57509

Closed
Tracked by #41316
hawkingrei opened this issue Nov 19, 2024 · 0 comments · Fixed by #57511
Closed
Tracked by #41316

flaky test TestMemTracker4InsertAndReplaceExec #57509

hawkingrei opened this issue Nov 19, 2024 · 0 comments · Fixed by #57511
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)

    oom_test.go:108: 
        	Error Trace:	pkg/executor/test/oomtest/oom_test.go:108
        	Error:      	Not equal: 
        	            	expected: ""
        	            	actual  : "background process exited"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-
        	            	+background process exited
        	Test:       	TestMemTracker4InsertAndReplaceExec

    oom_test.go:119: 
        	Error Trace:	pkg/executor/test/oomtest/oom_test.go:119
        	Error:      	Not equal: 
        	            	expected: ""
        	            	actual  : "initialize slot capacity"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-
        	            	+initialize slot capacity
        	Test:       	TestMemTracker4InsertAndReplaceExec

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.

1 participant