Previous job state information was "PENDING" rather than "REQUEUED"
  for each job requeued due to a burst buffer error.
bug 3388

scheduling a Datawarp job.

The assoc_mgr lock needs to happen before the bb_state.bb_mutex.  One place
this could cause deadlock is from src/slurmctld/controller.c
_accounting_cluster_ready() which calls clusteracct_storage_g_cluster_tres
which inturn calls bb_g_job_set_tres_cnt which calls bb_p_job_set_tres_cnt
which will lock the bb_muxtex after the assoc_mgr is already locked.

Bug 3389

Cache results of bit_set_count() calls.

Bug 3393.

Accidentally commited to Slurm version 16.05 instead of master

3 places where a string pointer referenced an out-of-scope memory location
1 memory leak and
1 unterminated string

backfill scheduler: Stop trying to determine expected start time for a job
    after 2 seconds of wall time. This can happen if there are many running jobs
    and a pending job can not be started soon.
byg 3373

mobile devices didn't behave as expected.

some of the tables (prolog_epilog) were hard to read.

Bug 3364.

Bug 3376.

Fix security issue caused by insecure file path handling triggered by
the failure of a Prolog script. To exploit this a user needs to
anticipate or cause the Prolog to fail for their job.

(This commit is slightly different from the fix to the 15.08 branch.)

CVE-2016-10030.

Fix security issue caused by insecure file path handling triggered by
the failure of a Prolog script. To exploit this a user needs to
anticipate or cause the Prolog to fail for their job.

CVE-2016-10030.

This modifies the logic in commit e089b63a for better clarity

Prevent "stray" jobs from using resources when the srun/salloc
will never launch the actual compute tasks.

Bug 3344.

PluginDir is allowed to be a PATH-style list of directories; remove
incorrect test of the variable as if it were a single directory and
comment that the check for that is elsewhere.

Bug 3361.

Expect is unable to work with more than 32-bit numbers, so it can't
properly test task affinity on KNL with 272 threads

- 2 x Integer handling issues (CONSTANT_EXPRESSION_RESULT)

Warning flag -Wempty-body in clang-3.7 now errors on this, split
macro definition up over multiple lines to silence.

Revision to 06fbdd75
  Previous logic was causing tests 1.87 and 15.19 to fail sometimes
  due to a race condition by adding a "Job allocation revoked"
  message to salloc output even if no allocation occured.
bug 3351

Previous logic was failing if no specialized cores configured on node
  and job wanted to configure some
bug 3349

Null terminate before strchr().

This is a new message when "PrologFlags=contain" or
  "PrologFlags=alloc" is configured.
bug 3351

Cancel interactive job if Prolog failure with "PrologFlags=contain"
    configured.
bug 3351

Minor fix to commit 1e6b7522 in
  the case where user specification of specialized cores is disabled.
bug 3349

If a job specifies --core-spec and the node has identified specialized
  cores using the CpuSpecList option which are not the default cores
  (e.g. the first cores rather than the last cores on each socket),
  the the user's cores will be selected from those identified in the
  configuration.
bug 3349

Was printing int64 using %ld, which generated a warning on some systems

Do not allocate specialized cores to jobs using the --exclusive option.
bug 3349

This commit should be part of b5f621d0
  when the man page was removed