Project

General

Profile

Actions

Bug #3136

closed

[Crunch] Job state is stale in Workbench pipeline instance views, if the job's state changes after the pipeline instance stops.

Added by Peter Amstutz over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Start date:
08/25/2014
Due date:
% Done:

100%

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

Description

Steps to reproduce:

  1. Run a pipeline
  2. Hit "Stop". This doesn't actually cancel the running jobs, see Bug #3165
  3. Go to the individual job page and cancel the job.
  4. Since the arv-run-pipeline-instance is no longer updating the copy of the job information in the pipeline instance record (why should it, it's stopped, right?) the pipeline will continue to show the job as running.

Quick resolution:

  • In Workbench, look up each job by UUID instead of rendering the copy of the job record stored in the pipeline instance.

Subtasks 2 (0 open2 closed)

Task #3327: Fix workbench display to only use the actual jobs and ignore denormalized copy of job data in components.ResolvedPeter Amstutz08/25/2014

Actions
Task #3676: Review 3136-stale-pipeline-instance-displayResolvedBrett Smith08/25/2014

Actions
Actions

Also available in: Atom PDF