Ah, okay. In this case I wanted to print out something to the user and
still succeed, as it was just a warning to the user that their script
had been modified.
Thanks.
-Paul Edmon-
On 01/29/2016 12:36 PM, [email protected] wrote:
It works for me, but only for the job_submit function (not job_modify)
and requires that the function return an error code (not "SUCCESS").
Here's a trivial example
function slurm_job_submit(job_desc, part_list, submit_uid)
slurm.log_user("TEST");
return slurm.ERROR
end
$ srun hostname
srun: error: TEST
srun: error: Unable to allocate resources: Unspecified error
Quoting Paul Edmon <[email protected]>:
So I've been working with the job_submit.lua part of our config, we
are running 15.08.7 and while slurm.log_info works, slurm.log_user
does not. My understanding is that slurm.log_user will print to the
users console. My code looks like the following:
slurm.log_user("Your current fairshare is not high enough to use the
priority partition. Your job has been automatically reset to the
following: %s",job_desc.partition)
Does any one see a problem with this? Does any one have a version of
job_submit.lua that uses slurm.log_user and it works? If so what is
the trick? Or am I misunderstanding what slurm.log_user does?
-Paul Edmon-
