Re: [slurm-users] Is this a bug in slurm array completion logic or expected behaviour

On Thu, Jan 30, 2020 at 7:54 AM Antony Cleave wrote: > epilog jobid=513,arraytaskid=4,SLURM_ARRAY_JOB_ID=509,JobState(509)=RUNNING > epilog jobid=514,arraytaskid=5,SLURM_ARRAY_JOB_ID=509,JobState(509)=RUNNING > epilog jobid=515,arraytaskid=6,SLURM_ARRAY_JOB_ID=509,JobState(509)=RUNNING > epilog j

[slurm-users] Is this a bug in slurm array completion logic or expected behaviour

Hi I want to run an epilogctld after all parts of an array job have completed in order to clean up an on demand filesystem created in the prologctld. First I though I could just assume that I could run the epilog after the completion of the final job step until I realised that they might not take