Skip to content
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

damit annotate Exited with exit code 140 #187

Open
CeciliaDeng opened this issue Jun 7, 2020 · 2 comments
Open

damit annotate Exited with exit code 140 #187

CeciliaDeng opened this issue Jun 7, 2020 · 2 comments

Comments

@CeciliaDeng
Copy link

Hi,

damit annotate completed ok to annotate 4 transcriptome assemblies but always failed for the other 2 transcriptomes. All 6 inputs were assembled using the same tool and in the same format (fasta). I tried several times to re-run the annotation. The failed message is usually "exit code 140", sometimes it's exit code 1 or 2. What do these exit codes mean? Is there anything wrong with the commands?

export TMPDIR=/path/to/project/tmp; dammit annotate $fasta --database-dir $dammitDB --full --busco-group eukaryota --n_threads 20 --output-dir $outputDir/R_eukaryota

Thank you.

@eburgueno
Copy link

eburgueno commented Jun 7, 2020

Exit code 140 is the job scheduler killing the job because it exceeds the queue runlimit (24 hours in our case). You can send the jobs to a different queue and see if that makes a difference.

Would still be curious to know about the other exit codes.

@camillescott
Copy link
Member

Thanks @eburgueno! I suspect that on occasion an individual program in the pipeline might be failing due to resource starvation just before the scheduler has the chance to kill the job, resulting in a code 1 or 2 rather than a 140.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants