Open
Description
Original report by Julian Zhou (Bitbucket: jqz, GitHub: julianqz).
Is there a way to catch such behaviour? There's hardly anything worse than waking up in the morning, fully expecting a job to have finished running, only to realize that a core dump had occurred and that the process was stuck on the AP step forever. Somehow this never triggers a job failure and never gets caught by slurm (happened multiple times to me so far).
SCAN_REVERSE> True
MIN_IDENT> 0.5
EVALUE> 1e-05
MAX_HITS> 100
FILL> False
ALIGNER> blastn
NPROC> 20
PROGRESS> 04:12:26 | | 0% ( 0) 0.0 min
PROGRESS> 04:14:05 |# | 5% ( 37,145) 1.7 min
PROGRESS> 04:15:44 |## | 10% ( 74,290) 3.3 min
PROGRESS> 04:17:24 |### | 15% (111,435) 5.0 min
PROGRESS> 04:19:04 |#### | 20% (148,580) 6.6 mi