Bug #3405
[Workbench] Pipeline runner errors not reported to user.
100%
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
History
#1
Updated by Peter Amstutz over 6 years ago
Updated by - Description updated (diff)
#2
Updated by Tom Clegg over 6 years ago
Updated by - Story points set to 0.5
#3
Updated by Tom Clegg over 6 years ago
- Target version set to 2014-08-27 Sprint
#4
Updated by Tom Clegg over 6 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 over 6 years ago
Similar problem if it tries to run a component with a required parameter is missing.
#6
Updated by Brett Smith over 6 years ago
Updated by Brett Smith - Assigned To set to Brett Smith
#7
Updated by Tim Pierce over 6 years ago
Updated by Tim Pierce - Category set to Workbench
#8
Updated by Brett Smith over 6 years ago
- Status changed from New to In Progress
#9
Updated by Peter Amstutz over 6 years ago
815549686de7aeaff01497bec88e11540ca0ad21
Without actually testing it, on visual inspection this looks good.
#10
Updated by Brett Smith over 6 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 over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:a5fbf74ba1454a555f2c74290e2ff08596955bb3.
Merge branch '3405-pipeline-error-logging-wip'
Closes #3405, #3582.