test: fix data conflict in TestCursorWillBlockMinStartTS
#55326
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: close #55227
Problem Summary:
There was a data conflict in the test, because the
MemTracker
is pre-allocated in the cache ofStatementContext
. If theStatementContext
is re-used, the mem tracker will be cleaned..What changed and how does it work?
Add a
ServerStatusCursorExists
flag. It makes sure theStatementContext
will not be re-used.Check List
Tests
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.