see bug 1047

Start a job in the highest priority partition possible, even if it requires
preempting other jobs and delaying initiation, rather than using a lower
priority partition. Previous logic would preempt lower priority jobs, but
then might start the job in a lower priority partition and not use the resources
released by the preempted jobs.
bug 1032

No change to logic

appears to be needed for make check

Recommend use of job arrays and multiple job steps per job.

Previously job would only run in first listed partition.

Fix gang scheduling for jobs submitted to multiple partitions.
Previous logic assumed the job's "partition" field contained a
single partition name, that in which the job is running. That
was recently changed in order to support job's being requeued,
which we want to be runable in all of it's valid partitions.

backport of commit 9b4f3634

signal 1.

done for normal steps.

of acting like it is a signal and exitcode.

previous it was always -2.

Apply BatchStartTimeout configuration to task launch and avoid aborting
srun commands due to long running Prolog scripts.
bug 978

Provide better description of the slurm.conf configuration parameter
BatchStartTimeout.
bug 979

When nodes scheduled for reboot, set state to DOWN rather than FUTURE so
they are still visible to sinfo. State set to IDLE after reboot completes.
bug 1007

suggest parentheses around assignment used as truth value.

The code tries to load libslurm.so even if precedent dlopen calls
succeeded. The code is structured so that we have to "return;" as
soon as a dlopen succeeds.

"job_comp/mysql" setting an incorrect default database.

Add logic to confirm that gres bitmaps exist before trying to use
them. We haven't seen this failure mode in v14.03, but in v14.11.

database index for the array elements avoiding duplicate database values.

job elapsed time.

the i/o thread.