Re: [slurm-users] getting started with job_submit_lua

2020-09-16 Thread Mark Dixon
On Wed, 16 Sep 2020, Niels Carl W. Hansen wrote: If you explicitely specify the account, f.ex. 'sbatch -A myaccount' then 'slurm.log_info("submit -- account %s", job_desc.account)' works. Great, thanks - that's working! Of course I have other problems... :( Cheers, Mark -- Mark Dixon Tel:

Re: [slurm-users] getting started with job_submit_lua

2020-09-16 Thread Diego Zuccato
Il 16/09/20 10:44, Mark Dixon ha scritto: > It seems "pairs" wasn't lying, job_desc really is empty? Nope. In my case, at least some fields are populated: .partition, .max_cpus (usually "a lot"), .max_nodes, .min_cpus, .min_nodes . I also tried adding local j = {} j.uid = submit_uid or -1

Re: [slurm-users] getting started with job_submit_lua

2020-09-16 Thread Niels Carl W. Hansen
If you explicitely specify the account, f.ex. 'sbatch -A myaccount' then 'slurm.log_info("submit -- account %s", job_desc.account)' works. /Niels Carl On Wed, 16 Sep 2020, Mark Dixon wrote: > On Wed, 16 Sep 2020, Diego Zuccato wrote: > ... > > From the source it seems these fields are availabl

Re: [slurm-users] getting started with job_submit_lua

2020-09-16 Thread Mark Dixon
On Wed, 16 Sep 2020, Diego Zuccato wrote: ... From the source it seems these fields are available: account comment direct_set_prio gres job_id Always nil ? Maybe no JobID yet? job_state licenses max_cpus max_nodes min_

Re: [slurm-users] getting started with job_submit_lua

2020-09-16 Thread Diego Zuccato
Il 15/09/20 19:47, Mark Dixon ha scritto: > I was expecting job_desc to be iterated over and show some interesting > stuff in my log, but it looks empty. Any ideas why that might be, please? Same thing I noticed. I needed it to check which fields were available, but it seems ipairs doesn't work as