correction to logic in commit c0919263

Move the real_size function to after the buffer has been setup
  per cray documentation

job array scripts were not being found in some cases

Don't treat an old version of dw_wlm_cli which does not support the
  real_size function as an error. Just log it using debug.

The Cray burst buffer (DataWarp) API syntax has changed. Modify test
  to work with new syntax.

Test system with old kernel doesn't define O_CLOEXEC, so partially
  revert commit b1ca7526

Bug 2892.

Bug 2874

We will most likely redo this logic (as it appears to be duplicated) in
a following patch.

bug 1884

No changes in logic

Don't generate an error when a batch job is submitted that must wait
  for stage-in before starting.

Bug 2886

Add new SchedulerParameters option of bb_array_stage_cnt=# to indicate
    how many pending tasks of a job array should be made available for burst
    buffer resource allocation.
bug 1884

Conflicts:
	src/sstat/options.c

Was incorrectly translating request to job.extern if part of a
comma-separate list.

Bug 2890.

bug 2858

bug 2858

(regression in 16.05.2).

related commit 5d3e5e1e

Bug 2612 and 2886

of the output.

'-' without a '\' in front of it.

Defaults to true, if set to false will not set kmem cgroup
limit. Bug 2748.

Document limitations in burst buffer use by the salloc command (possible
    access problems from a login node).
bug 2883

task/cgroup plugin is configured with ConstrainRAMSpace=yes, then set soft
    memory limit to allocated memory limit (previously no soft limit was set).
bug 2679

of 0.

This might be the cause of run away jobs.  I couldn't see how an end_time
could be 0, but if it was it would just exit and never set time_end to
anything.  At least if it happens now we can have an idea that it is
possible and we will have an idea this is the place it happens.

This will keep from referencing the task array that might not be set up
correctly in src/common/plugstack.c _spank_handle_init().