-
Notifications
You must be signed in to change notification settings - Fork 7
GitHub Issue 604: Improve JobRunner job tracking and completion waiting #7286
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
Conversation
| _executor.shutdown(); | ||
| } | ||
|
|
||
| public boolean awaitTermination(long timeout, @NotNull TimeUnit unit) throws InterruptedException |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that waitForCompletion() works for Runnables, isn't awaitTermination() redundant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regardless, a comment on these methods about use would be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I consolidated. They had different semantics but the distinction wasn't important.
Always shutdown runners in unit tests
Rationale
We should give equal handling to Runnables and Jobs
Changes