Open jaeddy opened 6 years ago
Most of my testing was done with WDL. CWL often doesn't print the relevant "success" line in its logs that status is checking for: https://github.com/common-workflow-language/workflow-service/blob/master/wes_service/toil_wes.py#L263
This was written and merged to address this: https://github.com/DataBiosphere/toil/pull/2339
Integrating the above toil status check into the toil backend should fix things.
When running the
md5sum.cwl
workflow using Toil, the job seems to hang indefinitely in "RUNNING" state. Looking at the run log, the workflow appears to have completed successfully, but the exit code is -1.Note: this occurred after installing from
master
, not my fork/branch used in #57.(eventually had to keyboard interrupt out of this step...)