Bug #4120

[Workbench] [obsolete?] Pipeline state can be failed even though every job is complete.

Added by Bryan Cosca over 3 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Start date:
10/10/2014
Due date:
10/10/2014
% Done:

0%

Estimated time:
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.

failed_complete.png (20.7 KB) failed_complete.png Bryan Cosca, 10/06/2014 09:02 PM

Related issues

Follows Arvados - Bug #4126: [SDKs] Parameter in pipeline runner is missingResolved2014-10-09

History

#1 Updated by Ward Vandewege over 3 years ago

  • Target version set to Bug Triage

#2 Updated by Radhika Chippada over 3 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

#3 Updated by Brett Smith over 3 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?

#4 Updated by Brett Smith over 3 years ago

My comment above describes the issue in #4126. This ticket is about displaying a consistent pipeline state when it happens.

#5 Updated by Brett Smith over 3 years ago

  • Due date deleted (10/08/2014)
  • Target version changed from Bug Triage to Arvados Future Sprints
  • Start date deleted (10/08/2014)

#6 Updated by Tom Clegg about 3 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.

#7 Updated by Tom Clegg about 3 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.

#8 Updated by Tom Clegg 11 months ago

  • Status changed from New to Closed

#9 Updated by Tom Clegg 11 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF