[FLINK-32144][connector/filesystem][test] Create a new minicluser instead of using MiniClusterExtension in tests that would kill JM/TM#23125
Merged
Conversation
…tead of using MiniClusterExtension in tests that would kill JM/TM Currently, MiniClusterExtension creates only one MiniCluster instance for each test class, all tests in the test class share one minicluster instance. So in the tests that would kill JM/TM, we have to manually create a new minicluster instance to avoid affecting other tests in the same class.
Collaborator
PatrickRen
approved these changes
Aug 8, 2023
Contributor
PatrickRen
left a comment
There was a problem hiding this comment.
@wanglijie95 Thanks for the patch! LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is the purpose of the change
Fix FLINK-32144, fix the unstable tests in
FileSourceTextLinesITCaseDoes this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation