Latest Release: 04/24/19
Release Notes can be found here.

Tasks that should be call-caching aren't

ebanksebanks Broad InstituteMember, Broadie, Dev ✭✭✭✭

I'm running a workflow that I just aborted halfway through and then restarted, expecting that all of the completed tasks from the original run would call-cache. While most of them did... some did not. The inputs to all of the tasks are the same (and Kristian just looked at my WDL over my shoulder and sanity checked it), so it should have just call-cached.

I don't care about this particular workflow for myself. I'm just reporting here as "something to make the product better". Specifically,
1) as a user I would want the ability to figure out why the hell my tasks didn't call cache, but it's just not something I can do right now
2) as a user I would want to save money when I could, so we should make sure it's working properly

Here's the original workflow:
https://portal.firecloud.org/#workspaces/genentech-prod-genomes/genentech-wdl-testing/monitor/05a6672d-8938-4624-b68d-e9dfbaa1cb7b

Here's the restarted one:
https://portal.firecloud.org/#workspaces/genentech-prod-genomes/genentech-wdl-testing/monitor/bd673c41-09de-4974-88c4-a3c5aa20ca9b/80d26763-0107-4555-a689-3c03a18bd5d7

I'll be out for a bit, so I've shared the workspace with @Geraldine_VdAuwera and have given her permissions to share further.

Thanks!

Best Answer

Answers

Sign In or Register to comment.