(regression in 16.05.2).

related commit 5d3e5e1e

Bug 2612 and 2886

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

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().

Prevent possible incorrect counting of GRES of a given type if a node has
    the multiple "types" of a given GRES "name", which could over-subscribe
    GRES of a given type.
bug 2836

The wrong variable was being used in gres.c to print a message of
this sort:
error: gres/gpu: job 7135 dealloc node ### type ### gres count underflow (# #)
The first number in the parenthesis was based upon the wrong index and it's
contents garbage

cleaning up on a restart.

sleep is killed.

for steps.

for a step.

hostlists when brackets == 0.

variable initialization lost in removing some debugging

Fix for invalid array pointer when creating advanced reservation when job
    allocations span heterogeneous nodes (differing core or socket counts).
bug 2876

Prevent backfill scheduler from starting a second "singleton" job if another
    one started during a backfill sleep.
related to bug 2808

Previous logic required listing each task of job array individually.
For example --dependency="afterany:123_4:123_5" can not be expressed
as --dependency="afterany:123_[4-5]".
bug 2644

we have the pids added to the system correctly.

Most likely related to bug 2874

Bug 2612 (and possibly others)

back to the slurmctld.