Actions
action #15386
closedContinue job already considered dead
Start date:
2016-12-08
Due date:
% Done:
0%
Estimated time:
Description
Description
A job considered dead by the web UI might be continued if it turns out it is still running when
- the job has not been duplicated yet
- the job has been duplicated but the duplicated job hasn't been started yet (is still scheduled)
Tasks
- prevent duplication or cancel duplicated job if already scheduled
- reassign worker, implementing https://progress.opensuse.org/issues/6564 before would be useful
- ensure job state transition from done to running doesn't cause any further trouble
Updated by mkittler over 7 years ago
- Related to action #6564: (re-)add Job::worker_id added
Updated by mkittler over 7 years ago
- Related to action #13952: too many warnings about dead workers in log added
Updated by mkittler over 7 years ago
- Status changed from New to Rejected
Instead increase timeout for dead jobs based on statistics.
Actions