Whew! I have use 'user_id' in a dozen other conditionals that I tested
exhaustively. After reading your first e-mail, I thought I was going crazy.
I suspect the issue is some sort of subtle typo or syntax error. I use
similar conditionals throughout my job_submit.lua script, and they all
work fine. I really hope someone on this list has more sensitive
eyeballs than I do.
Prentice
On 2/5/19 8:12 AM, Marcus Wagner wrote:
Hmm...,
no, I was wrong. IT IS 'user_id'.
Now I'm a bit dazzled
Marcus
On 2/4/19 11:27 PM, Prentice Bisbal wrote:
Can anyone see an error in this conditional in my job_submit.lua?
if ( job_desc.user_id == 28922 or job_desc.user_id == 41266 ) and
( job_desc.partition == 'general' or job_desc.partition ==
'interruptible' ) then
job_desc.qos = job_desc.partition
return slurm.SUCCESS
end
I am one if those user id's but if I submit a job to partition
'interruptible', without specifying a QOS, it still gets assigned to
the default QOS, which is 'general':
cat mpihello.sbatch
#!/bin/bash
#SBATCH -n 32
#SBATCH -p interruptible
#SBATCH -t 00:01:00
#SBATCH -J mpihello
#SBATCH -o mpihello-%j.out
#SBATCH -e mpihello-%j.err
#SBATCH --mail-type=ALL
module load gcc/7.3.0
module load openmpi/3.0.0
srun --mpi=pmi2 ./mpihello
$ scontrol show job 433953 | grep QOS
Priority=2512 Nice=0 Account=unix QOS=general
The logic of that conditional seems pretty simple, and I'm using
similar compound conditionals throughout my job_submit.lua script.
Can't figure out where the mistake is in this one.
