Re: [slurm-users] Job step do not take the hole allocation

2023-06-30 Thread Bjørn-Helge Mevik
Hei, Ole! :) Ole Holm Nielsen writes: > Can anyone she light on the relationship between Tommi's > slurm_cli_pre_submit function and the ones defined in the > cli_filter_plugins page? I think the *_p_* functions are functions you need to implement if you write a cli plugin in C. When you

Re: [slurm-users] Job step do not take the hole allocation

2023-06-30 Thread Ole Holm Nielsen
On 6/30/23 08:41, Tommi Tervo wrote: This was an annoying change: 22.05.x RELEASE_NOTES: -- srun will no longer read in SLURM_CPUS_PER_TASK. This means you will implicitly have to specify --cpus-per-task on your srun calls, or set the new SRUN_CPUS_PER_TASK env var to accomplish the

Re: [slurm-users] Job step do not take the hole allocation

2023-06-30 Thread Danny Marc Rotscher
Hi, thank you very much for your help! Best wishes, Danny > Am 30.06.2023 um 08:41 schrieb Tommi Tervo : > > smime.p7s Description: S/MIME cryptographic signature

Re: [slurm-users] Job step do not take the hole allocation

2023-06-30 Thread Tommi Tervo
> I searched the slurm.conf documentation, the mailing list and also the > changelog, but found no reference to a matching parameter. > Do anyone of you know the behavior and how to change it? Hi, This was an annoying change: 22.05.x RELEASE_NOTES: -- srun will no longer read in

[slurm-users] Job step do not take the hole allocation

2023-06-30 Thread Danny Marc Rotscher
Dear all, we currently see a change of a default behavior of a job step. On our old cluster (Slurm 20.11.9) a job step take all the resources of my allocation. rotscher@tauruslogin5:~> salloc --partition=interactive --nodes=1 --ntasks=1 --cpus-per-task=24 --hint=nomultithread salloc: Pending