was there for jobs and steps, but for no real reason.  I couldn't see a
reason anyway.

Add missing option for PURGE_JOB which is different than the others
and was missed on the changes made when adding the usage table
flushes.

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

Bug 3444

There are (or at least used to be) places where an exit code of 0 was used
to indicate that the job ran successfully to completion. This patch fixes
the places where the exit_code was MAX'd out to 1 to indicate that job did
not ran successfully to completion. This MAX logic was introduced in commit
f305f099.

Bug 3444

Conflicts:
	src/slurmctld/job_mgr.c

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

Bug 3444

bug 3448

Bug 3447

Bug 3444

These were false positive error reports, but should go away now.

Bug 3406.

Fix srun I/O race condtion to eliminate a error message that might be
    generated if the application exits with outstanding stdin.
bug 3166

# Conflicts:
#	META
#	NEWS

Use instead of the repeated construction of:
bit_not(b); bit_and(a, b); bit_not(b);
to avoid two addition iterations.

Can't set the job_id of a will_run will_run job prior to creating the
job. Invalidates the jobs for non-slurmuser jobs. Also not burning a
jobid could make the will_run job not be distinguishable in the logs.

Will handle the federation aspect of this in 17.11.

Bug 3436

job_write_lock and sleep a second before grabbing it again.  This should probably be made
configurable later on.

# Conflicts:
#	src/slurmctld/proc_req.c

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.

Properly set SLURM_JOB_GPUS environment variable for Prolog.
bug 3437