[SPARK-33793][TESTS][3.0] Introduce withExecutor to ensure proper cleanup in tests #30801
Conversation
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
…ng sure they are always stopped after the test.
Member
|
ok to test |
HyukjinKwon
changed the title
HyukjinKwon
approved these changes
Dec 16, 2020
srowen
approved these changes
Dec 16, 2020
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
HyukjinKwon
pushed a commit
that referenced
this pull request
Dec 16, 2020
…anup in tests Backport of: #30783 ### What changes were proposed in this pull request? This PR introduces a helper method `withExecutor` that handles the creation of an Executor object and ensures that it is always stopped in a finally block. The tests in ExecutorSuite have been refactored to use this method. ### Why are the changes needed? Recently an issue was discovered that leaked Executors (which are not explicitly stopped after a test) can cause other tests to fail due to the JVM being killed after 10 min. It is therefore crucial that tests always stop the Executor. By introducing this helper method, a simple pattern is established that can be easily adopted in new tests, which reduces the risk of regressions. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Run the ExecutorSuite locally. Closes #30801 from sander-goos/SPARK-33793-close-executors-3.0. Authored-by: Sander Goos <[email protected]> Signed-off-by: HyukjinKwon <[email protected]>
Member
|
Merged to branch-3.0. |
|
Test build #132885 has finished for PR 30801 at commit
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Backport of: #30783
What changes were proposed in this pull request?
This PR introduces a helper method
withExecutorthat handles the creation of an Executor object and ensures that it is always stopped in a finally block. The tests in ExecutorSuite have been refactored to use this method.Why are the changes needed?
Recently an issue was discovered that leaked Executors (which are not explicitly stopped after a test) can cause other tests to fail due to the JVM being killed after 10 min. It is therefore crucial that tests always stop the Executor. By introducing this helper method, a simple pattern is established that can be easily adopted in new tests, which reduces the risk of regressions.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Run the ExecutorSuite locally.