Heads up:
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
Update: July 26, 2019
This section of the forum is now closed; we are working on a new support model for WDL that we will share here shortly. For Cromwell-specific issues, see the Cromwell docs and post questions on Github.
This section of the forum is now closed; we are working on a new support model for WDL that we will share here shortly. For Cromwell-specific issues, see the Cromwell docs and post questions on Github.
Test for job failure
jmichael
Member ✭
I wrote an LSF backend and my WDL task is using more memory than I requested from LSF (from within a task) and so LSF kills the job. The problem is that the 'job' is the 'script' written by cromwell and the 'rc' file cannot be written since LSF kills the job.
In this case cromwell cannot detect job failure and so hangs forever. How do I integrate LSF such that cromwell can detect job failure? If LSF submits the script and the 'rc' file is only written from within the script then it can never be written if LSF kills the job.
Tagged:
Answers
Hi @jmichael,
The issue you're running into is being tracked here: https://github.com/broadinstitute/cromwell/issues/1499
Please follow and contribute to the discussion there if you'd like.
Thanks