action #23378
closed
[tools][sprint 201709.1] Enhancement and cleanup of "assigned" state
Added by okurz almost 7 years ago.
Updated over 6 years ago.
Category:
Regressions/Crashes
Description
When a job is stuck in the new "assigned" state the webUI does not offer a cancel button, it does not state when it was created or which worker it is assigned to. So "restart the worker" is not so easy when one does not know which worker.
- Copied from action #23364: Leap 42.2 aggregates tests not firing added
- Related to action #23320: [tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers/job restarts out of scheduler added
- Assignee changed from EDiGiacinto to szarate
- Status changed from New to In Progress
- Assignee changed from szarate to EDiGiacinto
- Status changed from In Progress to Resolved
- Subject changed from Enhancement and cleanup of "assigned" state to [tools][sprint 201709.1] Enhancement and cleanup of "assigned" state
Also available in: Atom
PDF