Open koadman opened 7 years ago
Note, this does not happen with non-MetaSweeper workflows
Were there any exceptions during the run? I have noticed that if I try and interrupt a running workflow with NF0.22.5 that the system will not return to the CLI and as you mention, requires SIGKILL (9).
hangs for me both with and without exceptions, while other (non-metasweeper) workflows exit cleanly on 0.22.5
Using vanilla nextflow 0.22.5 with any of the meta-sweeper workflows causes nextflow to simply hang at the end of the workflow, whether terminating cleanly or with error. A
kill -9
is required to terminate the process.