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

don't re-enqueue a successful job if worker is in SHUTDOWN_IMMEDIATE … #147

Merged
merged 1 commit into from
Aug 13, 2018
Merged

don't re-enqueue a successful job if worker is in SHUTDOWN_IMMEDIATE … #147

merged 1 commit into from
Aug 13, 2018

Conversation

bp-FLN
Copy link
Contributor

@bp-FLN bp-FLN commented Aug 4, 2018 •
edited
Loading

see #138

@bp-FLN bp-FLN force-pushed the successful-job-re-queue branch 3 times, most recently from 6329235 to 567cd78 Compare August 5, 2018 09:11
@coveralls
Copy link

coveralls commented Aug 5, 2018 •
edited
Loading

Coverage Status

Coverage decreased (-0.02%) to 70.637% when pulling 27519ee on uberall:successful-job-re-queue into 12884f9 on gresrun:master.

@gresrun
Copy link
Owner

gresrun commented Aug 13, 2018

Thanks again! I'll merge once the spelling fix is in.

@gresrun gresrun merged commit 9ac3111 into gresrun:master Aug 13, 2018
@bp-FLN bp-FLN deleted the successful-job-re-queue branch August 13, 2018 20:21
@bp-FLN bp-FLN mentioned this pull request Aug 16, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gresrun gresrun gresrun requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@bp-FLN @coveralls @gresrun