Skip to content

Conversation

brndnmtthws
Copy link
Member

If a job has 0 repititions remaining, but the schedule is in the past,
it'll cause the sleep time to be return as 0. This might fix #803.

If a job has 0 repititions remaining, but the schedule is in the past,
it'll cause the sleep time to be return as 0. This might fix #803.
@brndnmtthws brndnmtthws force-pushed the fix-nanosUntilNextJob-edgecase branch from a68625c to f0f7e7c Compare February 24, 2017 02:32
@brndnmtthws brndnmtthws merged commit 7eff5e0 into master Feb 24, 2017
@brndnmtthws brndnmtthws deleted the fix-nanosUntilNextJob-edgecase branch February 24, 2017 02:36
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.

Chronos response becomes very slow when there are a lot of tasks

1 participant