Skip to content
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

Use a dedicated thread pool rather than Timer.get for DurableTaskStep.Execution.check #53

Merged
merged 5 commits into from
Oct 13, 2017

Conversation

jglick
Copy link
Member

@jglick jglick commented Sep 27, 2017

Analogous to #44. Downstream of jenkinsci/workflow-support-plugin#46.

@reviewbybees

….Execution.check, since it has often been observed to block for a while.
@jglick jglick requested review from abayer and svanoort September 27, 2017 20:00
@ghost
Copy link

ghost commented Sep 27, 2017

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

Otherwise we get thread dumps showing many blocked calls to DurableTaskStep$Execution.check
with no indication of which agent is failing to respond.
@jglick
Copy link
Member Author

jglick commented Sep 27, 2017

Very flaky tests. Looking into it.

…dition: aborting an execution is not guaranteed to cancel node {} queue items synchronously.
@jglick
Copy link
Member Author

jglick commented Sep 29, 2017

@reviewbybees done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants