Only mark job_id as zero for batch step (when all job steps would be
cleared), not for individual steps which prevented successive steps
from being cancelled.

Bug 2984.

slurmstepd modified to pre-load all relevant plugins at startup to avoid
    the possibility of modified plugins later resulting in inconsistent API
    or data structures and a failure of slurmstepd.
bug 2334

bug 2655

Add more details to the log messages for improved ability to
diagnose problems.

Bug 2983.

Continuation of 18947480. Commit cff2effc made cpu_freq_init
unconditionally set up the structures, so this reinitialization was
discarding the true original info, which prevents the frequency
and governor from being restored properly after the step completes.

Don't about step launch if job reaches expected end time while node is
    configuring/booting (NOTE: The job end time will be adjusted after node
    becomes ready for use).
bug 2985

The sleep starts at 0.1 second and doubles each time to a
  maximum value. Previous maximum was 2 seconds, increased
  to 5 seconds to account for very large KNL boot times
  (tens of minutes) and to limit overhead on slurmctld daemon.

If the KNL node modes reported by cnselect and capmc differ, log
  that using "info" rather than "debug".

frequency other than AcctGatherNodeFreq.

Filesystem instead of Lustre.

Network dataset.

Locking slurmstepd in memory can result in exhausting real memory
  in some cases, resulting in failure of the slurmstepd process.
  This reverts commit 03cf4a5d,
  but the logic will be returned using a configuration parameter
  in Slurm version 17.02.
bug 2334

This should improve performance and prevent failure if a local
  group ID lookup fails.
bug 2928

Minor correction to commit 30baec8d

Prevent slurmd abort if hwloc library fails to populate the "children"
    arrays (observed with hwloc version "dev-333-g85ea6e4").

Bug 2955.

Document the partition limits considered in the EnforcePartLimits
logic.
bug 2920

Correction to commit b45a55bc
but 2920

Make EnforcePartLimit support logic work with any ordering of partitions
    in job submit request.
Developed jointly with Alejandro Sanchez <alex@schedmd.com>
bug 2920

Calculation switched the node count in place of the cpu count, which
results in incorrect estimates.

CID 44784.

CID 44787.

Bug 2950. Also identified as CID 56684 (copy+paste error).

CID 45023 and 45024.

Fix task:CPU binding logic for some processors. This bug was introduced
in version 16.05.1 to address KNL bunding problem.
bug 2972

Needed due to part_filter_set() calls; without write lock this can race
returning inconsistent results to 'sinfo'.

Bug 2958.

Regression test fixes if SelectTypePlugin not managing memory and no node
    memory size set (defaults to 1 MB per node).

Fix race condition in the account_gather plugin that could result in job
    stuck in COMPLETING state.
bug 2973

These problems have been around for a while, but coverity just started
  to report them for some reason.

Prior logic used to create an advanced reservation based upon a core
  count would ignore the specialized cores. Then when a job tried to
  use the reservation, it would consider the specialized cores and
  not be able to use the core count used in the reservation creation.
  This change considers specialized cores when creating the reservation.