Add the pack count argument to slurm_step_launch() function in
  test suite and perl api. The argument was added in commit
  71a34f56

Modify launch/slurm plugin to signal all components of a pack job rather
   than just the one (modify to use a list of step context records).

If prolog is running when attempting to signal a step, then return EAGAIN
   and retry rather than simply returning SLURM_ERROR and aborting.

Fix I/O race condition on step termination for srun launching multiple
   pack job groups. Without this change application output might be
   lost and/or the srun command might hang after some tasks exit.

All of these were pre-existing Coverity errors, but I changed nearby
code, variable names, etc. so they looked like new errors.

Coverity reported problem, CID 45194

CID 44936

Coverity CID 171494

variables

This restores perl API operation after commit aea2f0e2

Bug 3956.

Add translation code for the RPCs as well.

Bug 3956.

Add pack_job_id and pack_job_offset to accounting database.
Modified sacct to accept pack job ID specification using "#+#" notation.
Modified sstat to accept pack job ID specification using "#+#" notation.

NULL is returned if the token is not found, testing against '\0'
is wrong (although does work okay in older compilers).

Fixes new GCC 7.1 warning.

was matching more than expected.

error messages that aren't really errors.

Related to Bug 3997

Without this change, each component would generate separate
  email at job begin, end, etc.

If the pack job allocation partially failed, properly handle accounting
  and deallocation of burst buffer. Note, this should rarely happen.

Bug 3999

Default to 1, unless set to 0. Allow to be set to 0 even if
GroupUpdateTime was not set before.

Move down to alphabetical position in read_config.c as well.

Bug 3956.

Fix bug in selection of GRES bound to specific CPUs where the GRES count
    is 2 or more. Previous logic could allocate CPUs not available to the job.

bug 4029

NULL is returned if the token is not found, testing against '\0'
is wrong (although does work okay in older compilers).

Fixes new GCC 7.1 warning.

Highlight the need to use Slurm abstract CPU ID

When the node isn't actually rebooted, the BootTime isn't updated and
Slurm doesn't consider that the node is returned to service, even
if slurmd is responding.

Bug 4039

This will be fixed before 17.11, but is being left as-is on 17.02.

Bug 3956.