Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Option --clean=never is not being respected by toil-wdl-runner
See original GitHub issueI use vocab.wdl and run this:
toil-wdl-runner --jobStore=toilWorkflowRun --logDebug --clean=never --stat vocab.wdl vocab.json
I get this:
INFO:toil.leader:Finished toil run successfully.
INFO:toil.common:Successfully deleted the job store: FileJobStore(/localdisk/.../toilWorkflowRun)
How do I keep the job-store with the WDL runner? Or does restart simply not work with completed WDL workflows?
┆Issue is synchronized with this Jira Story ┆Issue Number: TOIL-36
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Setting the Stage: Why Health Care Needs a Culture of Respect
Respect for patients. Equally, if not more important, is respect for our patients. All patients deserve to be treated with dignity and an ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@davidlougheed Yes, that’s the culprit. I’ll take a look and see about a fix.
I noticed this line https://github.com/DataBiosphere/toil/blob/5538d4eea8279243504c234d34709e27cfee0e2c/src/toil/wdl/wdl_synthesis.py#L209 which seems to manually always set clean to always for WDL jobs