-
Notifications
You must be signed in to change notification settings - Fork 7
Cannot reuse a outDir on aws #680
Comments
Mentionned that to Paolo on gitter, and:
|
can confirm that this issue exists. I have the same problem. |
Maybe sth to do with the
|
This error is also triggered when starting variant calling and using the same outDir as was used for preprocessing. This is a bit more annoying than if one is only rerunning the preprocessing since one would not get the preprocessing in the same outdir as the variantcalling... |
Even more annoying is that this completely blocks annotation from being run on AWS since it has to find the VariantCalling within the outDir: Line 49 in 35e7f70
Line 68 in 35e7f70
However, I think I'm starting to understand this error. Reading the log carefully:
I narrowed it down to
and indeed if one adds the following to the conf:
it's possible to launch the pipeline. However, I suspect the other reports will cause the pipeline to fail when the final job is done. |
fixed by #682 |
Describe the bug
When using a outDir on s3 which already exists, I get the error
ERROR ~ Unexpected error [UnsupportedOperationException]
To Reproduce
Steps to reproduce the behavior:
--outDir
Expected behavior
It should use that directory I guess?
System (please complete the following information):
Nextflow (please complete the following information):
Sarek (please complete the following information):
The text was updated successfully, but these errors were encountered: