Bug 5476.

SLURM_FAILURE removed in a76a9486.

Leads to false-positive warnings about settings being too low when
they're actually fine. E.g., if innodb_buffer_pool_size is over 2GB
the warning would have been printed in error.

Bug 5661.

Bug 5594.

You should not make RPC calls within MailProg (or anything else
fork()+exec()'d from slurmctld), so use the environment variable that
is now exposed instead.

Bug 5443.

smail currently uses 'scontrol show config' to get this data; making RPC
calls within programs fork()+exec()'d from slurmctld is best avoided as
it amplifies RPC load on the controller.

Bug 5443.

Fix formatting on the log_level documentation block as well.

Bug 5399.

Add info to man page as well.

Bug 4961.

Bug 5724

For some reason this file had all sorts of bad indenting.

Bug 5724

Bug 5231

Bug 5708

This matches the functionality in code.

Bug 5726

Bug 5795

Continuation of 06582da8 (17.11.9)

Poll was timing out too quickly due to an incorrect conversion of
MessageTimeout. Added a multiplier so timeout reflects the correct
millisecond value.

Bug 5553

Coverity CID 188467

"set errno to indicate error" made some think that the function had
to explicitly set the errno before returning, when it is often done
by sub functions.

Bug 5376

Replace these with either SLURM_ERROR or SLURM_SUCCESS

Bug 5392

# Conflicts:
#	src/common/gres.c

# Conflicts:
#	src/common/slurm_protocol_pack.c
#	src/slurmctld/controller.c

This adds the ability for a step to explicitly clear a job's gres counter.
For example, the job requests --gpus-per-task=2 and the step requests
--gpus-per-task=0.

change some comments and log messages.
no change in functionality

failing to propagate gpus-per-task for job step

Since sacct exits the program when it finds unknown parameters, the
debug2() statements should be escalated to error() statements.
The first debug2() even had "Error: " in it.
Get rid of extra newline.

Bug 5421

Bug 5786

Bug 5165

Bug 5743.

Co-authored-by: Dominik Bartkiewicz <bart@schedmd.com>

Move reused GRES parsing logic to a shared function.

(Corrected author; was previously mis-committed as 433257c6.)

Bug 5743.

This reverts commit 433257c6.

This just tests the gpus-per-node option. Additional tests are
needed for gpus-per-task, etc. as well as the logic to support
those options for job steps.

Bug 5165

It was still possible for job priority to go down to 0, because I was
letting last_prio get set down to 1, then later on we were using
last_prio-1 as the new job priority. Since last_prio was 1, then new
job priority was 1-1=0. This happened when the job priorities were all
at 2 (which I never tested). Michael found it by running test2.26 in a
case where initial job priorities were 2:

spawn /home/marshall/slurm/18.08/voyager/bin/squeue --name=test2.26 -o JOB_ID=%A PRIO=%Q
JOB_ID=JOBID PRIO=PRIORITY
JOB_ID=10702 PRIO=2
JOB_ID=10703 PRIO=2
JOB_ID=10704 PRIO=2
Reset and test job priorities

spawn /home/marshall/slurm/18.08/voyager/bin/scontrol top 10704,10703
spawn /home/marshall/slurm/18.08/voyager/bin/squeue --name=test2.26 -o JOB_ID=%A PRIO=%Q
JOB_ID=JOBID PRIO=PRIORITY
JOB_ID=10704 PRIO=2
JOB_ID=10703 PRIO=1
JOB_ID=10702 PRIO=0
Reset and test job priorities

Fix memory leak in previous patch.

Bug 5479

Coverity 188464