[slurm-users] Re: Access to --constraint= in Lua cli_filter?

2024-08-19 Thread Kevin Buckley via slurm-users
On 2024/08/19 15:11, Ward Poelmans via slurm-users wrote: Have a look if you can spot them in: function slurm_cli_pre_submit(options, pack_offset) env_json = slurm.json_env() slurm.log_info("ENV: %s", env_json) opt_json = slurm.json_cli_options(options) slurm.log_info("OPTIONS: %

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Bjørn-Helge Mevik via slurm-users
Brian Andrus via slurm-users writes: > IIRC, slurm parses the batch file as options until it hits the first > non-comment line, which includes blank lines. Blank lines do not stop sbatch from parsing the file. (But commands do.) -- B/H signature.asc Description: PGP signature -- slurm-use

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Brian Andrus via slurm-users
IIRC, slurm parses the batch file as options until it hits the first non-comment line, which includes blank lines. You may want to double-check some of the gaps in the option section of your batch script. That being said and you say you removed the '&' at the end of the command, which would

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Davide DelVento via slurm-users
Since each instance of the program is independent and you are using one core for each, it'd be better to leave slurm deal with that and schedule them concurrently as it sees fit. Maybe you simply need to add some directive to allow shared jobs on the same node. Alternatively (if at your site jobs m

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Arko Roy via slurm-users
Dear Loris, I just checked removing the & it didn't work. On Mon, Aug 19, 2024 at 1:43 PM Loris Bennett wrote: > Dear Arko, > > Arko Roy writes: > > > Thanks Loris and Gareth. here is the job submission script. if you find > any errors please let me know. > > since i am not the admin but just

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Loris Bennett via slurm-users
Dear Arko, Arko Roy writes: > Thanks Loris and Gareth. here is the job submission script. if you find any > errors please let me know. > since i am not the admin but just an user, i think i dont have access to the > prolog and epilogue files. > > If the jobs are independent, why do you want to

[slurm-users] Re: Unable to run sequential jobs simultaneously on the same node

2024-08-19 Thread Arko Roy via slurm-users
Thanks Loris and Gareth. here is the job submission script. if you find any errors please let me know. since i am not the admin but just an user, i think i dont have access to the prolog and epilogue files. If the jobs are independent, why do you want to run them all on the same node? I am running

[slurm-users] Re: Access to --constraint= in Lua cli_filter?

2024-08-19 Thread Ward Poelmans via slurm-users
Hi Kevin, On 19/08/2024 08:15, Kevin Buckley via slurm-users wrote: If I supply a   --constraint= option to an sbatch/salloc/srun, does the arg appear inside any object that a Lua CLI Filter could access? Have a look if you can spot them in: function slurm_cli_pre_submit(options, pack_offse