sbatch --ntasks option to take precedence over --ntasks-per-node plus node
    count, as documented. Set SLURM_NTASKS/SLURM_NPROCS environment variables
    accordingly.
bug 2015

Previous logic would report an error and stop the power_save thread.
bug 2042

Not sure when that went away...

If a suspended job is manually resumed and gang scheduling is
configured, but no time slices are available for the job being
resumed, then just resume it without adding it to a time slice.
The jobs previously running on those nodes will be replaced with
new jobs as resources become available and the resumed job will
basically be treated like a stray job.
bug 2031

Avoid reporting more allocated CPUs than exist on a node. This can be
    triggered by resuming a previosly suspended job, resulting in
    oversubscription of CPUs.
bug 2021

bug 2031

Add scancel -f/--full option to signal all steps including batch script and
    all of its child processes.
bug 2031

Bug 1888

out.

Remove unneeded code that commit 8274ea54 fixed.

This code would 0 out all GRES/TRES on a reconfig which isn't what we want.

8274ea54 does the right thing by itself.

bug 2032

bug 2039

bug 2037

backport of commit 4f2e2801 from v16.05

Needed to change a couple of variables from 32- to 64-bit.

Add new burst_buffer.conf parameters: ValidateTimeout and OtherTimeout.
See man page for details.

previously take 2 restarts of the slurmdbd to make it stick correctly.

single-threaded cores.  A regression caused only 1 socket to be used on
this kind of node instead of all that were available.

If a job allocation returns some invalid contents, the pointer
  to the job structure may be NULL. This change preserves the error
  message and avoids a segv.

Fix case where if the backup slurmdbd has existing connections when it gives up control that the it would be killed.

If the backup had existing connections when giving up control, it would try to
signal the existing threads by using pthread_kill to send SIGKILL to the
threads. The problem is that SIGKILL doesn't go the thread but the main process
and the backup dbd would be killed.

when a cold-start (-c) happens to the slurmctld.

Conflicts:
	src/sacct/options.c

from a user.

This would cause the slurmctld to cache the old default which wasn't valid
and cause the user to have to request the association always.

Conflicts:
	NEWS
	src/plugins/accounting_storage/mysql/as_mysql_job.c

bug 2009