multiple versions.

on the most recent pmix_vX.so file.
One is free to directly use new "pmix_vX" plugin names as well.

NOTE: there is one small artifact introduced by this fix - there will be
no "pmix" name in the output of "srun --mpi=list" but the most recent plugin
will be duplicated:

$ ./srun --mpi=list
srun: MPI types are...
srun: mpi/none
srun: mpi/mvapich
srun: mpi/mpich1_shmem
srun: mpi/mpichgm
srun: mpi/pmix_v1      <----
srun: mpi/mpichmx
srun: mpi/lam
srun: mpi/pmi2
srun: mpi/openmpi
srun: mpi/mpich1_p4
srun: mpi/pmix_v1      <----

conflicting pmix versions.

linking against.

commit 20a73c508e1.

of what is in the header file of pmix.

To ease the distribution process, plugin names will be automatically
adjusted to identify the version of API that it can support,
ie: pmix_v1 and pmix_v2.
This provides the ability for distro's to create separate
non-conflicting packages for each API generation.

Bug 2986

Insure reported expected job start time is not in the past for pending jobs.
bug 3002

burst_buffer/cray: Requeue, but do not hold a job which fails the pre_run
    operation.
bug 3009

Bug 2984.

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").