Bug #12840
closed
[Workbench] Don't show cancelled pipeline instances as failed
100%
Description
Currently if you cancel a job, it gets marked as cancelled along with its child jobs, but the pipeline instance itself gets marked as "Failed" making for a misleading display if you're just looking at a top level listing of pipeline instances.
Updated by
Updated by Tom Morris almost 7 years ago
- Target version changed from 2018-01-17 Sprint to 2018-01-31 Sprint
Updated by Tom Clegg almost 7 years ago
- Target version changed from 2018-01-31 Sprint to 2018-02-14 Sprint
Updated by Tom Clegg almost 7 years ago
12840-cancelled-pipeline @ 948c4e583b89e28730f8a0d2ae3f94e459351b30
Updated by Lucas Di Pentima almost 7 years ago
Looking for examples, I came across this one:
https://workbench.qr1hi.arvadosapi.com/pipeline_instances/qr1hi-d1hrv-nqpy9zwnbn7ra38
...it seems that it should be marked as “Failed” instead of “Cancelled” because as I could read on the logs, it had some docker issue that stopped it from running.
Updated by Tom Clegg almost 7 years ago
In qr1hi-d1hrv-nqpy9zwnbn7ra38 the failure was "couldn't create job", so there's no job with state=Failed. It does have components_summary[failed]=1 though, so that could also trigger the "Failed" display.
Updated by Tom Clegg almost 7 years ago
12840-cancelled-pipeline @ 2517c98e6835fef0a9e9829773f058d7ced00462
Updated by Anonymous almost 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|5d164d74505c232cfa232d69a56273da2d02b72a.