This is a new field and the fix only applies to an emulated burst
  buffer configuration (i.e. dw_wlm_cli script made to look like
  a real DataWarp system)

Change error() to verbose(). New logic is needed to address this issue
   once we know how to determine the KNL MCDRAM size.

cray/burst_buffer - Preserve job ID and don't translate to job array ID
  after slurmctld restart. Prior logic would not set array_task_id to
  NO_VAL, so all job-buffer IDs would be reported in the form
  "JobID=0_0(123)" rather than "JobID=123"

cray/busrt_buffer - Internally track both allocated and unusable space.
    The reported UsedSpace in a pool is now the allocated space (previously was
    unusable space). Base available space on whichever value leaves least free
    space.
bug 3222

Previously disconnected from build system, and most code removed by
commit 0b14a3a7 back on 15.08-pre1.

We don't build on Tru-64, and there are a lot more platform-dependent
pieces of code within Slurm than we've indicated here.

Remove stray Bull logo as well.

Remove stray Bull logo as well.

They're full of dead links, and the plugins are deprecated
(announced at SLUG16).

OSX is not currently supported, and the build is likely broken
due to differences in dynamic library loading.

Add LaunchParameters=mem_sort option to set configur running of zonesort
    by default at step startup.
Also add documentation about zonesort on KNL web page
bug 3188

and request --ntasks-per-core=1 and only 1 task on the node
the slurmd would abort on an infinite loop fatal.

Regression is from commit 5265420d.

Without this fix you can get into an infinite loop in the task/affinity
plugin.  The loop is handled by producing a fatal.

Bug 3118

Type is required for cray persistent burst buffer creation

cray/busrt_buffer - Fix for double counting of used_space at slurmctld
    startup.
bug 3222

Add the POLLRDHUP hack used elsewhere to work around non-standard flag use.

Bug 3227.

cray/busrt_buffer - If total_space in a pool decreases, reset used_space
    rather than trying to account for buffer allocations in progress.
bug 3222

bug 3188

If a cluster was removed from a federation, then the cluster's send was
left around.

salloc/sbatch -w node0 -n2 to allocate 2 nodes instead of only 1 if it
could.

This makes the code look like it does in srun which does do the correct
thing.

The core_resrcs ptr was being dropped on the floor because
unpack_job_resources() allocates its own job_resources_t ptr.

the step table yet, so this patch is invalid.

a job could be accounted for more than it should in the _decay_thread
inside the priority/multifactor plugin.  Before the end_time_exp wasn't
stored for the job which was what was used to determine if the job was
already processed or not.  In 16.05 we were able to fix this mostly, but
for the TRES numbers they could get accounted for multiple times.  Since
a pack was needed to fix this we had to wait until 17.02.