On Friday, 23 November 2018 10:21:09 PM AEDT Matthew Goulden wrote:
> I've spent some time reading through the (excellent, frankly) documentation
> for sbatch and job_exit_code and while learning a great deal nothing has
> explained with anomaly.
I suspect Slurm is trying to be helpful, as exit c
Hi;
As far as I know exit code 141 and 13 are the same. Signal + 128 gives
exit code:
https://slurm-dev.schedmd.narkive.com/MYGH56EW/job-exit-codes
Ahmet M.
On 23.11.2018 14:36, Matthew Goulden wrote:
A confirmation re-run yielded the same outcome but the correct outcome
was available
A confirmation re-run yielded the same outcome but the correct outcome was
available using
$ scontrol show job 197
JobState=FAILED Reason=NonZeroExitCode Dependency=(null)
Requeue=1 Restarts=0 BatchFlag=1 Reboot=0 ExitCode=141:0
sacct still reports as before
$ sacct -j 197
JobID
Hi All,
New using migrating from uge/sge, I'm baffled by the ExitCode recording into
slurmdb; not sure if this is 'new user' issue or bug, so exposing it here first.
Running simple sbatch scripts with these headers relevant
#!/bin/bash
#SBATCH --mail-user @
#SBATCH --mail-type END
#SBATCH -
