Actions
Bug #4120
closed
[Workbench] [obsolete?] Pipeline state can be failed even though every job is complete.
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Story points:
-
Description
The instance : pipeline_instances/qr1hi-d1hrv-x86anyj6ublq1vp completed with a valid output but the current state says failed.
I expected it to say it succeeded.
Files
Related issues
Updated by
Updated by Radhika Chippada over 9 years ago
- Subject changed from current state:failed when job is complete to [Workbench] current state:failed when job is complete
- Category set to Workbench
Updated by Brett Smith over 9 years ago
The start of the log says:
2014-10-06 20:56:06 +0000 -- pipeline_template qr1hi-d1hrv-x86anyj6ublq1vp Errors: first::b - required parameter is missing
It looks like arv-run-pipeline-instance is misjudging when a pipeline is runnable. The template at issue does say that a b parameter is required, but it also provides a value. Maybe a-r-p-i doesn't consider that this value will be used for the pipeline instance?
Updated by Brett Smith over 9 years ago
My comment above describes the issue in #4126. This ticket is about displaying a consistent pipeline state when it happens.
Updated by Brett Smith over 9 years ago
- Due date deleted (
10/08/2014) - Target version changed from Bug Triage to Arvados Future Sprints
- Start date deleted (
10/08/2014)
Updated by Tom Clegg over 9 years ago
- Subject changed from [Workbench] current state:failed when job is complete to [Workbench] Pipeline state can be failed even though every job is complete.
Updated by Tom Clegg over 9 years ago
- Subject changed from [Workbench] Pipeline state can be failed even though every job is complete. to [Workbench] [obsolete?] Pipeline state can be failed even though every job is complete.
Updated by Tom Clegg about 7 years ago
- Target version deleted (
Arvados Future Sprints)
Actions