We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SAMTOOLS_SORT is failing in local tests (-profile test, docker), but working on farm (-profile test,sanger,singularity):
-profile test, docker
-profile test,sanger,singularity
ERROR ~ Error executing process > 'SANGERTOL_VARIANTCALLING:VARIANTCALLING:INPUT_MERGE:SAMTOOLS_SORT (icCanRufa1_cram_T1)' Caused by: Process `SANGERTOL_VARIANTCALLING:VARIANTCALLING:INPUT_MERGE:SAMTOOLS_SORT (icCanRufa1_cram_T1)` terminated with an error exit status (1) Command executed: samtools cat \ GCA_947369205.1.unmasked.pacbio.icCanRufa1_0_3.cram \ | \ samtools sort \ \ -T icCanRufa1_cram_T1 \ --threads 2 \ --reference GCA_947369205.1_OX376310.1_CANBKR010000003.1.fasta.gz \ -o icCanRufa1_cram_T1.bam \ - cat <<-END_VERSIONS > versions.yml "SANGERTOL_VARIANTCALLING:VARIANTCALLING:INPUT_MERGE:SAMTOOLS_SORT": samtools: $(echo $(samtools --version 2>&1) | sed 's/^.*samtools //; s/Using.*$//') END_VERSIONS Command exit status: 1 Command output: (empty) Command error: [main_cat] ERROR: input is not BAM or CRAM [W::hts_set_opt] Cannot change block size for this format samtools sort: failed to read header from "-"
No response
The text was updated successfully, but these errors were encountered:
Not high priority. It is some sort of arm incompatibility -- works fine if I run a terminal with rosetta emulation
Sorry, something went wrong.
tkchafin
No branches or pull requests
Description of the bug
SAMTOOLS_SORT is failing in local tests (
-profile test, docker
), but working on farm (-profile test,sanger,singularity
):Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: