Bug 4620

find jobs that ran on specific nodes.

Bug 4602

needed if you are ever working with multi-dimensional systems.

Bug 4602

This isn't a real problem, but older compilers will complain about it.
Newer compilers know in order to get into the place it could be used
'have_count' would have to be set.  If that is set then feature_list
would also be set.

itself.

Bug 4638

Test 3.11, file inc3.11.9 only runs for some configurations, but
  assumes no leading zeros in node name suffix. When run with
  nodes named "nid[00001-00005]", the test converted the last
  number to it's numeric for and as making requests for
  "nid[00001-5]", which would fail.

Fix output file containing "%t" (task ID) for heterogeneous job step to
    be based upon global task ID rather than task ID for that component
    of the heterogeneous job step.

This expands some comments
Explicitly sets some pointers to NULL after memcpy (these are
   redundant, but add clarity) and
Move a memcpy to avoid modifying the wrong values

Fix for possible memory corruption in srun when running heterogeneous
job steps.
bug 4626

This partially reverts 89bcd975 and aac6bd39

Turns out you can't use a list_for_each and lock something inside the
list_for_each function that does a lock without the write lock.

Bug 4611

This reverts commit ff3e77f4.

This partially reverts 89bcd975 and aac6bd39

Turns out you can't use a list_for_each and lock something inside the
list_for_each function that does a lock without the write lock.

Bug 4611

Otherwise undocumented, and does not do anything.
Will be removed in 18.08.

Fix job array dependency with "aftercorr" option and some task arrays in
    the first job fail. This fix lets all task array elements that can run
    proceed rather than stopping all subsequent task array elements.
Bug 4590

Creating a copy of the actual environment in env->env defines a new pointer,
then next call to setup_env and setenvf doesn't define variables in the global
environment but in this new copy.

Bug 4615

This fixes the problem introduced in by commit
777a45f9 and maintains proper PMIx
operation.
bugs 4132 and 4615

node_feature/knl_cray - Fix memory leak that can occur during normal
    operation. This will happen when an update request for a specific
    node happens.

If CnselectPath and/or SyscfgPath defined in knl_cray.conf file and
  slurmctld reconfigured, the original values of those paraemters
  would be over-written and their memory leaked.

Use FREE_NULL_BUFFER instead, otherwise we could attempt to
free_buffer a second time if we jump to the rwfail label.

bug4491

to preempt other eligible jobs.

Bug 4279

Missing from 390da8cf

Bug 4595

slurmdb_pack_assoc_usage() will assert with a NULL usage ptr.

7d9a75df uncovered that slurmdb_pack_assoc_usage() expects a usage
ptr.

Bug 4469

This is a continuation to c539d346 where this should had been removed
in the first place.

Bug 4127

bug 4539

When --mail-type option isn't requested with ARRAY_TASKS, we need somehow
to summarize the different states each task finished in the array. We've
added a new ARRAY_TASK_REQUEUED flag to the array_flags to indicate that
at least one task was requeued. Also the logic now detects if at least
one task failed and/or if otherwise all finished successfully.

The patch also removes the RunTime from the the e-mail when summarizing
whole array, since it doesn't make sense to specify just the RunTime
of one of the tasks for this case.

Patch also fixes when ARRAY_TASKS is specified, previously the mail
notification for the master job task record included a range of
ExitCodes for all the tasks. Since this option is not for summarizing,
the patch makes it so only the range is shown when the option isn't
specified.

Bug 4539.