Closed jxshi closed 2 years ago
yes, this one was giving me a hard time as well.
The very issue is well known for many years in the old samtools code: https://github.com/lh3/samtools/pull/7
But why we are hitting it here, I am not sure. In the debugger if you delete the viral.bam and re-creates just well.
I've made the samtools call safer here: https://github.com/bcbio/bcbio-nextgen/pull/3582
And it seems to be solving the issue in my bcbio run.
Let me know how it works for you (you'd need to upgrade to the latest code).
Sergey
Hi @naumenko-sa ,
I circumvented this issue by turning off viral
in the template yaml
file with the following option.
tools_off:
- viral
And finally, it went through. Cheers!
Best, Jianxiang
Thanks for confirming! In my project, it finished with multicore bcbio (one-node, as opposed to ipython).
see also this fix: https://github.com/bcbio/bcbio-nextgen/pull/3587
Version info
bcbio_nextgen.py --version
): 1.2.9alsb_release -ds
): CentOS Linux release 7.8.2003 (Core)To Reproduce Exact bcbio command you have used:
Your yaml configuration file:
Log files (could be found in work/log) Please attach (10MB max):
bcbio-nextgen-commands.log
, andbcbio-nextgen-debug.log
.bcbio-nextgen-commands log
bcbio-nextgen-debug.log