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.

Sign up for GitHub

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

Jump to bottom

Clarify pre_shutdown_timeout behavior in new_kill_child comment #1543

Merged
merged 1 commit into from
Feb 22, 2017
Merged

Clarify pre_shutdown_timeout behavior in new_kill_child comment #1543

merged 1 commit into from
Feb 22, 2017

Conversation

corincerami
Copy link
Member

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 82.863% when pulling 3a3ddb6 on chrisccerami:clarify_pre_shutdown_timeout_in_comment into 71a2764 on resque:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 82.863% when pulling 3a3ddb6 on chrisccerami:clarify_pre_shutdown_timeout_in_comment into 71a2764 on resque:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 82.863% when pulling 3a3ddb6 on chrisccerami:clarify_pre_shutdown_timeout_in_comment into 71a2764 on resque:master.

@corincerami corincerami force-pushed the clarify_pre_shutdown_timeout_in_comment branch from 3a3ddb6 to b619dc4 Compare February 22, 2017 05:10
@coveralls
Copy link

coveralls commented Feb 22, 2017 •
edited
Loading

Coverage Status

Coverage remained the same at 82.863% when pulling b619dc4 on chrisccerami:clarify_pre_shutdown_timeout_in_comment into 71a2764 on resque:master.

@corincerami corincerami merged commit 51e6265 into resque:master Feb 22, 2017
@corincerami corincerami deleted the clarify_pre_shutdown_timeout_in_comment branch February 22, 2017 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@corincerami @coveralls