Closed
Bug 844547
Opened 13 years ago
Closed 10 years ago
Crontabber should explicitly mark skipped jobs
Categories
(Socorro :: Backend, task)
Socorro
Backend
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: lonnen, Assigned: peterbe)
Details
Crontabber explicitly tracks consecutive errors, but leaves skips to be inferred. This can cover up some error conditions in the overnight runs. Crontabber should explicitly mark when a job is skipped and keep track of how many times it is skipped. Errors and skips should both hang around until a successful run, then they should be cleared.
Targeting this for 36. Cherry-pick it to stage if it's done in time.
|
Assignee | |
Updated•13 years ago
|
Target Milestone: 36 → 37
|
|
Assignee | |
Updated•13 years ago
|
Target Milestone: 37 → 38
|
|
Assignee | |
Updated•13 years ago
|
Target Milestone: 38 → 40
|
|
Assignee | |
Updated•13 years ago
|
Target Milestone: 40 → Future
|
Reporter | |
Comment 1•10 years ago
|
||
I'm not sure we need this. Last run and next run times have been good enough.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•