WIthout this patch, when the slurmd cold starts or slurmstepd
terminates abnormally, the job script file can be left around.
bug 243

Previously such a job submitted to a DOWN partition would be queued.
bug 187

a reservation when it has the "Ignore_Jobs" flag set.  Since jobs could run
outside of the reservation in it's nodes without this you could have
double time.

This is not applicable with launch/aprun

These changes are required so that select/cray can load select/linear,
  which is a bit more complex than the other select plugin structures.
Export plugin_context_create and plugin_context_destroy symbols from
  libslurm.so.
Correct typo in exported hostlist_sort symbol name
Define some functions in select/cray to avoid undefined symbols if
  the plugin is loaded via libslurm rather than from a slurm command
  (which has all of the required symbols)

cluster.

If step requests more CPUs than possible in specified node count of job
allocation then return ESLURM_TOO_MANY_REQUESTED_CPUS rather than
ESLURM_NODES_BUSY and retrying.

Without this change, when the sbatch --export option is used, many
Slurm environment variables are not set unless explicitly exported.

success

This problem would effect systems in which specific GRES are associated
with specific CPUs.
One possible result is the CPUs identified as usable could be inappropriate
and job would be held when trying to layout out the tasks on CPUs (all
done as part of the job allocation process).
The other problem is that if multiple GRES are linked to specific CPUs,
there was a CPU bitmap OR which should have been an AND, resulting in
some CPUs being identified as usable, but not available to all GRES.

options in srun, and push that logic to salloc and sbatch.

Bug 201

and timeout in the runjob_mux trying to send in this situation.

Bug 223

The original reservation data structure is deleted and it's backup
added to the reservation list, but jobs can retain a pointer to the
original (now invalid) reservation data structure.
Bug 250

energy data.

Without this fix, jobs that should be initiated by the backfill
scheduler based upon the preemption of other jobs will not be
started.

cnode does not have a job running on it do not resume the block.

Select/cons_res - If the job request specified --ntasks-per-socket and the
allocation using is cores, then pack the tasks onto the sockets up to the
specified value. Previously it would ignore the ntasks-per-socket
parameter and distribute tasks across sockets

--enable-debug.

Counts would previously go negative as jobs terminate and decrement from
a base value of zero