Bug #3973

[Workbench] After cloning a pipeline instance, the new instance should not have any cancelled jobs/components

Added by Tim Pierce almost 5 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Start date:
09/24/2014
Due date:
% Done:

0%

Estimated time:
Story points:
0.5

Description

On pipeline qr1hi-d1hrv-pr1aen5iz9x7zrv, the allelotype_run component of the pipeline was cancelled. When the pipeline instance is re-run, this component remains cancelled in new runs.

History

#1 Updated by Tim Pierce almost 5 years ago

  • Description updated (diff)

#2 Updated by Tim Pierce almost 5 years ago

  • Subject changed from cloned pipeline instance also clones 'cancelled_by' to cancelled jobs remain cancelled when pipeline instance is re-run
  • Description updated (diff)
  • Target version changed from Bug Triage to Arvados Future Sprints

#3 Updated by Tom Clegg almost 5 years ago

  • Subject changed from cancelled jobs remain cancelled when pipeline instance is re-run to [Workbench] After cloning a pipeline instance, the new instance should not have any cancelled jobs/components
  • Story points set to 0.5

Also available in: Atom PDF