The behaviour seems to be diffrent in slurm 15.08 at least.
sacct --format=JobID,Elapsed,AllocCPUS,CPUTimeRaw -j 7364851
JobID Elapsed AllocCPUS CPUTimeRAW
------------ ---------- ---------- ----------
7364851 00:00:00 16 0
7364851.0 00:00:00 1 0
sacct -X --format=JobID,Elapsed,AllocCPUS,CPUTimeRaw -j 7364851
JobID Elapsed AllocCPUS CPUTimeRAW
------------ ---------- ---------- ----------
7364851 00:00:00 16 0
/Magnus
On 2016-03-23 09:29, Magnus Jonsson wrote:
Hi!
From this simple example could someone explain to me if this is the
expected behaviour or a bug?
$ srun -n1 --exclusive hostname
srun: job 4232239 queued and waiting for resources
srun: job 4232239 has been allocated resources
host0001.example.com
$ sacct -X --format=JobID,Elapsed,AllocCPUS,CPUTimeRaw -j 4232239
JobID Elapsed AllocCPUS CPUTimeRAW
------------ ---------- ---------- ----------
4232239 00:00:03 48 144
$ sacct --format=JobID,Elapsed,AllocCPUS,CPUTimeRaw -j 4232239
JobID Elapsed AllocCPUS CPUTimeRAW
------------ ---------- ---------- ----------
4232239 00:00:03 1 144
We are currently running 14.03 but the same behaviour exist in 14.11 as
well.
I see that the TRES-feature change a lot of this in the 15+ releases but
does it change this behaviour (I don't have access to any 15 cluster
right now)?
Best regards,
Magnus
--
Magnus Jonsson, Developer, HPC2N, Umeå Universitet
