Re: [slurm-users] Odd behavior/bug with --array env

2018-02-20 Thread Robert Anderson
--array expectedcurrent 0-15:4 15 12 0-14:4 14 12 0-13:4 13 12 0-12:4 12 12 0-11:4 11 8 Given a specified array of work I expected to get a reference to the full array. Your explanation of step as sequence shorthand

[slurm-users] CPUAlloc incorrect value

2018-02-20 Thread Stéphane Larose
Hi all, I have a single server with 64 cores. The first 4 cores are reserved for slurm daemons (CPUSpecList=0-3) and for ssh connections. So slurm have 60 cores to assign jobs to. I do not know why but at a certain time, the CPUAlloc value becomes incorrect and wrongly calculated. For example,

Re: [slurm-users] Odd behavior/bug with --array env SLURM_ARRAY_TASK_MAX

2018-02-20 Thread E V
Well isn't the next job index 10, when counting by 5 and you specified a max index of 9, so 5 is the max that will run for your specification. On Mon, Feb 19, 2018 at 4:06 PM, Robert Anderson wrote: > While working on an example python slurm job script I found the > environment variable SLURM_ARR