You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using some tasks from here: https://github.com/broadinstitute/long-read-pipelines/blob/dc2cd65fe18e9301925f88cc79a3db601cd38029/wdl/tasks/Utility/Finalize.wdl (specifically FinalizeToDir) and I ran into some esoteric cases where call-caching was failing to re-upload results even when the underlying files had been updated. While the issues with call-caching might or might not be relevant here I actually think all of the upload tasks in that WDL should be labeled as meta { volatile: true } since their behavior depends on the status of files in the output folder which is not checked by cromwell for call-caching, so they should not be call-caching lest the state of the output folder be incorrect.
The text was updated successfully, but these errors were encountered:
I was using some tasks from here: https://github.com/broadinstitute/long-read-pipelines/blob/dc2cd65fe18e9301925f88cc79a3db601cd38029/wdl/tasks/Utility/Finalize.wdl (specifically FinalizeToDir) and I ran into some esoteric cases where call-caching was failing to re-upload results even when the underlying files had been updated. While the issues with call-caching might or might not be relevant here I actually think all of the upload tasks in that WDL should be labeled as
meta { volatile: true }
since their behavior depends on the status of files in the output folder which is not checked by cromwell for call-caching, so they should not be call-caching lest the state of the output folder be incorrect.The text was updated successfully, but these errors were encountered: