-
Notifications
You must be signed in to change notification settings - Fork 134
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
[#612] test: cleanup shuffleServer instance for each test #658
Conversation
LGTM. Is there any other occurrences(tests) to stop shuffle server for each test? |
It depends on whether the test cases use exclusive or shareable shuffle servers. |
OK. Let's fix that when other test cases have similar problem. |
Thanks @advancedxy |
@zuston Could you cherrypick and commit to branch 0.7 branch, too. |
### What changes were proposed in this pull request? Cleanup shuffleServer instance for each test ### Why are the changes needed? When digging into the root cause of #612, I found some problems that the shuffle server instance should be released after each test case is finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Don't need
…he#658) ### What changes were proposed in this pull request? Cleanup shuffleServer instance for each test ### Why are the changes needed? When digging into the root cause of apache#612, I found some problems that the shuffle server instance should be released after each test case is finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Don't need
What changes were proposed in this pull request?
Cleanup shuffleServer instance for each test
Why are the changes needed?
When digging into the root cause of #612, I found some problems that the shuffle server instance should be released after each test case is finished.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Don't need