Actions
Bug #21993
open
Workflow runner keeps running when its only subprocess is "on hold" (state=queued, priority=0)
Story points:
-
Description
Steps to reproduce:
- Launch a workflow that starts with a single step (e.g.: revsort) and wait for the wf runner instance to start
- Wait for the subprocess appears as Queued
- Cancel the subprocess
The workflow runner instance will keep running indefinitely. Not sure if it's a-c-r's job to realize that it should cancel itself.
Files
Related issues
Updated by Lucas Di Pentima 13 days ago
- Description updated (diff)
- File stuck-wf.png stuck-wf.png added
Updated by Brett Smith 13 days ago
- Related to Bug #20985: Setting priority 0 on a queued container should change it to "cancelled" state added
Updated by Peter Amstutz 12 days ago
Yes, arvados-cwl-runner should notice that the priority went to 0 and do something about it.
Actions