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

If a pack job is only partitially allocated resources (likely due
  due to limits), deallocate resources from those components which
  have been started and requeue them.

Previous logic could corrupt a pack job's tres_alloc_count array
resulting in slurmctld's accounting module abort.

Perform limit check on heterogeneous job as a whole at submit time to
   reject jobs that will never be able to run. Accepting pack jobs
   that can never start will have a significant effect on scheduling
   in general (blocking the queue).

This change adds a new function and moves some logic around so that
  limits can be tested on a pack job as a whole (that logic still
  needs to be developed).

This should never happen, but if we start some pack job components
and for unexpected reasons fail to start others at the same time,
the components that remain pending will be able to start at a later
time so long as the other components can either
1. start at the same time OR
2. have already been started

Adds assocation and QOS limits for the pack job as a whole

Don't requeue a batch pack job component that is not found node zero of
the allocation. Only the first pack job component is expected to have a
running script.

Clear a job's "wait reason" value of BeginTime" after that time has
passed. Previously a readon of "BeginTime" could be reported long
after the job's requested begin time had passed (for so long as the
current reason is "None".

Add support to sched/backfill for concurrent allocation of all pack job
      components including support of --time-min option.

Don't try to launch pack job component ID != 0
  Make pack job batch test38.2 more robust
  Add completion time data to backfill data structure to support
  deadline and min-time options

This is a work in progress, not ready for use yet.

This removes several define statements with different names in
  various functions

Fix for possible slurmctld abort with use of salloc/sbatch/srun
    --gres-flags=enforce-binding option.
bug 4008

Update from commit b40bd8d3

Clarify --immediate option.

By removing the real locks we can get into a race condition where the prolog
starts and finishes before we get here and then we end up waiting forever.

Making the mutex a static seemed to help in many cases, but didn't
completely close the window.  Changing slurm_cond_wait to
slurm_cond_timedwait fixed the scenario where we would hit the window, but
not degrade performance the original commit provides.

There were also spots where if the job or step didn't exist it wouldn't
signal the conditional also providing a spot this could get stuck not
starting the job.

Fix regression from commit 52ce3ff0

Bug 3977

Fix for debugger setup bug introduced in commit
f1110568

Avoid interleaving labels and output from various components of
   a pack job

This allocates an array to the proper size (based upon all tasks
  to be launched). Work still needed to populate the data structure
  properly for all tasks.

No change in logic

The debugger symbol in srun is not being properly handled today.
  This change does the malloc once, even for a pack-job, makes
  the array over-sized, and range checks before writes. Suitable
  for making srun progress without memory errors (writing off end
  of allocated memory in an array).