Correct some cgroup paths ("step_batch" vs. "step_4294967294", "step_exter"
    vs. "step_extern", and "step_extern" vs. "step_4294967295").

Requeue/hold batch job launch request if job already running. This is
  possible if node went to DOWN state, but jobs remained active.
In addition, if a prolog/epilog failed DRAIN the node rather than
  setting it down, which could kill jobs that could continue to
  run.
bug 1985

Bug 1938

Bug 1984

When nodes have been allocated to a job and then released by the
  job while resizing, this patch prevents the nodes from continuing
  to appear allocated and unavailable to other jobs. Requires
  exclusive node allocation to trigger. This prevents the previously
  reported failure, but a proper fix will be quite complex and
  delayed to the next major release of Slurm (v 16.05).
bug 1851

When nodes have been allocated to a job and then released by the
  job while resizing, this patch prevents the nodes from continuing
  to appear allocated and unavailable to other jobs. Requires
  exclusive node allocation to trigger. This prevents the previously
  reported failure, but a proper fix will be quite complex and
  delayed to the next major release of Slurm (v 16.05).
bug 1851

Add ability to change a job array's maximum running task count:
    "scontrol update jobid=# arraytaskthrottle=#"
bug 1863

option.

The 2 came from the nodelist being "None assigned", which would be treated
as 2 hosts when sent into hostlist.

the default qos for the association.

jobs.

Bug 1969

Pending job array records will be combined into single line by default,
    even if started and requeued or modified.
bug 1759

diversion.

only 1 job was accounted (against MaxSubmitJob) for when an array was
submitted.

Correct counting for job array limits, job count limit underflow possible
    when master cancellation of master job record.
bug 1952

Implement an option NONE for not sending mails
at all.
Closes http://bugs.schedmd.com/show_bug.cgi?id=1962

only 1 job was accounted (against MaxSubmitJob) for when an array was
submitted.

Fix teardown race condition that can result in infinite loop.
bug 1947

This prevents a step from being launched if the job is killed
while the prolog is running. Reproducing the original failure
requires use of srun to trigger the prolog and using scancel
while that prolog is running.
bug 1755

anomaly when only asking for 1 (task_id was never set to INFINITE).

This prevents a step from being launched if the job is killed
while the prolog is running. Reproducing the original failure
requires use of srun to trigger the prolog and using scancel
while that prolog is running.
bug 1755

And add missing documenation.
Bug 1921

GRES were not being properly tracks for multiple simultaneous steps.
A step which could have run later could be rejected as never being
able to run.
Replacement for commit dd842d79, which was reverted in commit 6f73812875c
bug 1925

and you use all the GRES up instead of reporting the configuration isn't
available you hold the requesting step until the GRES is available.