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
The D version of Sambamba is in maintenance mode. Use the github issue
tracker to report bugs only. For comments, questions and features,
please use the google group mailing list as stated on the README!
When I run this command in interactive shell the command finishes in 20 seconds. But if I run it in python subprocess, in parallel (silcing the same bam file with different bed region files), it sometimes run into a situation where the command runs for hours (like 20 -40 hours according to my observation) and in htop interface, the job is always in an R status instead of stay in dormant (S or other status) and the CPU usage is around 100%. I'm so confused and having trouble to reproduce the issue if not run the entire pipeline.
To Reproduce
seems that I cannot reproduce the error to you guys instantly with any small samples. I just wonder whether my description will remind you of any similar issues you've been dealt with ? I cannot find any similar issues in the github issues section though. Thanks.
The sambamba version I'm using is 1.0.0. Thanks.
The text was updated successfully, but these errors were encountered:
Only bug reports!
The D version of Sambamba is in maintenance mode. Use the github issue
tracker to report bugs only. For comments, questions and features,
please use the google group mailing list as stated on the
README!
Describe the bug
The command is like this:
"""
sambamba slice -q -L xxx.bed xxx.bam | sambamba view -q -F "xxx" -f sam /dev/stdin | sort - | uniq -
"""
When I run this command in interactive shell the command finishes in 20 seconds. But if I run it in python subprocess, in parallel (silcing the same bam file with different bed region files), it sometimes run into a situation where the command runs for hours (like 20 -40 hours according to my observation) and in htop interface, the job is always in an R status instead of stay in dormant (S or other status) and the CPU usage is around 100%. I'm so confused and having trouble to reproduce the issue if not run the entire pipeline.
To Reproduce
seems that I cannot reproduce the error to you guys instantly with any small samples. I just wonder whether my description will remind you of any similar issues you've been dealt with ? I cannot find any similar issues in the github issues section though. Thanks.
The sambamba version I'm using is 1.0.0. Thanks.
The text was updated successfully, but these errors were encountered: