Bug 3472

regcomp() is not safe to use across a fork in older glibc versions.
Reinitialize the keyvalue_re structure after the fork through an atfork()
handler.

Bug 3276.

Honor --ntasks-per-node and --ntasks option when used with job constraints
    that contain node counts.
bug 3458

Defer interactive job allocation until ALL allocated nodes are ready
  rather than after PrologSlurmctld (if any) completes.

Bug 3467.

burst_buffer/cray - Do not execute "pre_run" operation until after all nodes
    are booted and ready for use.
bug 3461

Insure job does not start running before node is booted and PrologSlurmctld
    is complete.
bug 3446

Ported from 7a4aa7f2.

and make it so the slurmd formats it correctly when it comes in.

Continuation of commit 7db90c8a

This is needed to make it so we can run pmix with multi-slurmd.

Bug 3446

bug 3446

burst_buffer/cray - Support default pool which is not the first pool
    reported by DataWarp and log in Slurm when pools that are added or removed
    from DataWarp.
bug 3453

This reverts commit fd690a9c.

sstat doesn't work on Cray ALPS but works on native Cray setups.

Jobs preempted with PreemptMode=REQUEUE were incorrectly recorded as
REQUEUED in the accounting.

Bug 3444

bug 3448

Bug 3447

Bug 3444

e3a7bdcc
f9804256
d72b13f2

Reference bug 3366

If you are running on a Bluegene system we rely on the prolog to take us out of configuring
state.  These commits work good for system rebooting the nodes where the prolog is running,
but in the case of Bluegene this is the opposite desire :).   These commits on a Bluegene
pretty much make it so a batch job never gets launched.

Clear job's reason of "BeginTime" in a more timely fashion and/or prevents
    them from being stuck in a PENDING state. There are multiple ways of
    clearing the reason, especially on a lightly loaded system, but the
    state can persist indefinitely on a heavily loaded system.
bug 3368

Fix to logic for getting expected start time of existing job ID with
    explicit begin time that is in the past. Previous logic would
    compare that (past) begin time with advanced reservations that
    would compete with it rather than the current time.

On cray systems with step NHC, the step launches are delayed and
  produce a pair of messages (below) that caused the test to fail:
  srun: Job step creation temporarily disabled, retrying
  srun: Job step created