New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline hangs when all processes execution are skipped #43
Comments
Unfortunately like the previous one I'm not able to reproduce the problem however I'm almost sure that I've patched it. Please give a try to the patch that I've just uploaded following the usual steps:
It should print this output:
|
@yesimon I've forgot to mention you. Please have a look to the above comment. |
Ok that specific bug looks like it's fixed, but now I get a different nondeterministic bug. This one crops up much rarer, about 1/10 runs when poolSize is 1. Doesn't seem to occur with larger poolSize but might have to run it more.
.nextflow.log: |
I think this new error trace is related to the fact that you are using a thread pool with one thread. That does not make a lot of sense in a parallelisation framework. If it arise even when using more than one thread, please open a new issue. I will try to investigate it with the Gpars guys. |
Makes sense. If unfixable throw an error when trying to run with one thread? |
Actually there are two thread pools. One that executes the user tasks and another used by the Gpars parallelisation library. A better strategy could be to set the |
See the log file in the above link and the example at #41
https://gist.github.com/yesimon/cf59053d90ee3ea6c700
The text was updated successfully, but these errors were encountered: