Compiler errors out preventing these 13 from running without fixing the implied
int type for main.

though we decided to push that fix to 16.05 since this has been broken for
a while and no one has complained.

Avoid error message of "Requested cpu_bind option requires entire node to
    be allocated; disabling affinity" being generated in some cases where
    task/affinity and task/cgroup plugins used together.

restart of the slurmctld.

On some systems the char_to_val was not being put into the plugin,
resulting in the following error:
slurmstepd: [23.0]: symbol lookup error: /home/jette/SLURM/install_smd/lib/slurm/task_cgroup.so: undefined symbol: char_to_val
The problem was fixed by declaring the function "static". The
function was name was also updated with a leading "_" to indicate
the function is local to that module.

Otherwise miscalculated limit will lead to job cancellation even when well
inside the allocated amount.

Bug 2660.

in the slurmdbd segfaulting.

Bug 2656

burst_buffer/cray - Don't call Datawarp "paths" function if script includes
    only create or destroy of persistent burst buffer. Some versions of Datawarp
    software return an error for such scripts, causing the job to be held.
bug 2624

No change in any logic or definitions

If a job fails stage in, set its reason to BurstBufferOperation
with a string describing what happened. Previously the reason was
set to AdminHeld on stage-in failure.

that wasn't set up correctly.

power/cray - Fix bug introduced in 15.08.10 preventin operation in many
    cases.
bug 2628

Was printing integer using %u format

burst_buffer/cray - Fix for script creating or deleting persistent buffer
    would fail "paths" operation and hold the job.
bug 2624

and it doesn't meet basic requirements.

The gprof tool is showing most time is being consumed by the bit_test()
  function as called from the select plugin, which in turn was called
  by the backfill scheduler. These changes replace the for loop end-points.
  Previous logic tested for all possible nodes. The new logic identifes
  the first and last bit set in the node bitmap and uses those end-points
  instead. Node the logic to find the first and last bits set starts off
  with a word-based search (testing for a 64-bit zero value rather than
  testing each individual bit). The net result is a small performance
  improvement.
bug 2588

burst_buffer/cray - Decrement job's prolog_running counter if pre_run fails.
bug 2621

If a job is no longer in configuring state, then clear the prolog_running
  counter on slurmctld restart or reconfigure.
bug 2621

For case where job can't start and there are no running jobs
to remove in order to establish estimated start time.

When determining when a pending job will be able to start, rather
  than testing after removing each running job and trying to schedule
  the pending jobs, remove multiple jobs that all end about the
  same time before testing. This reduces the number of calls to
  the job placement logic, which is time consuming.

list_peek_next(), like list_next() but WITHOUT advancing the pointer

Document and log cases where max jobs per user or partition is
  equal or greater than the max jobs test. In that case, a single
  user can easily stop all backfill scheduling.

Fix for job "--contiguous" option that could cause job allocation/launch
    failure or slurmctld crash.
bug 2573

This reverts commit f559a55c.

constraints mattered in a job.

Details include:
A job doesn't request memory but the system is running
with CR_*MEMORY with no default memory limit and the job requests nodes
with features of different sizes.  Previously the order of constraints
mattered where the smaller memory node would need to be requested first
or the job would fail.

Bug 2608

Previous logic would get an account and/or QOS time limit and use
  that value to overwrite the incoming RPC's NO_VAL value, which
  would change a job's time limit when changing an unrelated
  field (e.g. priority, QOS, etc.).
bug 2610