Previous logic required listing each task of job array individually.
For example --dependency="afterany:123_4:123_5" can not be expressed
as --dependency="afterany:123_[4-5]".
bug 2644

we have the pids added to the system correctly.

Most likely related to bug 2874

Bug 2612 (and possibly others)

back to the slurmctld.

Add salloc/sbatch/srun --spread-job to distribute tasks over as many nodes
    as possible. This also treats the --ntasks-node-node option as a maximum
    value. For example "srun -n16 --ntasks-per-node=2 --spread-job ..." will
    run the job on at least 8 nodes (with 2 tasks each), but will attempt to
    use as many nodes as possible up to the task count (1 task per node).
bug 2732

prctld(PR_GET_NAME) >= 2.6.11

This reverts commit d9d36a33.

In bug #1499, customer asked to precisely identify which srun options apply
to job allocations, which to step allocations and which apply to both. So
the srun man page has been updated with this information.

Move test for job wait reason value of BurstBufferResources and
    BurstBufferStageIn later in the scheduling logic. This will
    result in job reasons related to QOS, account, and partition
    limits to be displayed instead of burst buffer (if applicable)
bug 2835

id wasn't able to be made.

Discovered in testing that the cnselect command only returns information
  about KNL node state for nodes that are already up. If a node is down
  or in the process of booting, only capmc as the state which will be in
  effect when the boot completes. This change merges the old logic (reading
  state from capmc) with new logic (merging new state information from
  cnselect into the capmc data), which results in the most complete
  picture possible about the KNL state.
bug 2850

Values are already time_t / printed with %ld so this should
keep Y2038 at bay.

Bug 2862.

Bug 2864.

Discovered in testing that the cnselect command only returns information
  about KNL node state for nodes that are already up. If a node is down
  or in the process of booting, only capmc as the state which will be in
  effect when the boot completes. This change merges the old logic (reading
  state from capmc) with new logic (merging new state information from
  cnselect into the capmc data), which results in the most complete
  picture possible about the KNL state.
bug 2850

Bug 2855.

node_features/knl_cray plugin modified to get current node MCDRAM
   mode using cnselect command rather than capmc command. This gets the
   current BIOS setting, which could differ from what is configured to be
   set on boot, at least if something other than Slurm is modifying
   KNL modes.
bug 2850

node_features/knl_cray plugin modified to get current node NUMA mode using
    cnselect command rather than capmc command. This gets the current
    BIOS setting, which could differ from what is configured to be
    set on boot, at least if something other than Slurm is modifying
    KNL modes.
bug 2850