Bug #3405

[Workbench] Pipeline runner errors not reported to user.

Added by Peter Amstutz about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
Workbench
Target version:
2014-08-27 Sprint
Start date:
08/12/2014
Due date:
% Done:

100%

Estimated time:
(Total: 1.00 h)
Story points:
0.5

Description

I created a pipeline that arv-run-pipeline-instance wasn't happy with (bad script_parameter definition), but no error was logged to the pipeline runner page, instead the pipeline never started the first job.

Subtasks

Task #3582: Review 3405-pipeline-error-logging-wipResolvedPeter Amstutz

Associated revisions

Revision a5fbf74b
Added by Brett Smith about 5 years ago

Merge branch '3405-pipeline-error-logging-wip'

Closes #3405, #3582.

Revision 5596c93b (diff)
Added by Tom Clegg about 5 years ago

Update Gemfile.lock. refs #3405

History

#1 Updated by Peter Amstutz about 5 years ago

  • Description updated (diff)

#2 Updated by Tom Clegg about 5 years ago

  • Story points set to 0.5

#3 Updated by Tom Clegg about 5 years ago

  • Target version set to 2014-08-27 Sprint

#4 Updated by Tom Clegg about 5 years ago

  • Subject changed from Pipeline runner errors not reported to user. to [Workbench] Pipeline runner errors not reported to user.

#5 Updated by Peter Amstutz about 5 years ago

Similar problem if it tries to run a component with a required parameter is missing.

#6 Updated by Brett Smith about 5 years ago

  • Assigned To set to Brett Smith

#7 Updated by Tim Pierce about 5 years ago

  • Category set to Workbench

#8 Updated by Brett Smith about 5 years ago

  • Status changed from New to In Progress

#9 Updated by Peter Amstutz about 5 years ago

815549686de7aeaff01497bec88e11540ca0ad21

Without actually testing it, on visual inspection this looks good.

#10 Updated by Brett Smith about 5 years ago

Peter Amstutz wrote:

815549686de7aeaff01497bec88e11540ca0ad21

Without actually testing it, on visual inspection this looks good.

I tested it on our test cluster with success. I had to twiddle the states that could be flipped to failed, but otherwise it's good. Thanks.

#11 Updated by Brett Smith about 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:a5fbf74ba1454a555f2c74290e2ff08596955bb3.

Also available in: Atom PDF