Otherwise the recently newly added '#include <lua.h>' condition will
break the build on systems without any Lua installation.

Follow on to commit 7cc4d0d8. Bug 3681.

This also fixes the fed_mgr on the backup slurmctld to start backup
correctly if the backup takes control more than once.

Bug 3827

It will result in the job being held if it is requeued at a later time.

Bug 3751.

Previously, incorrect partitions and duplicated partition names
could be shown.

The array needs to be incremented by two, not one, as each
element is a start-end pair.

Bug 3793.

when configured with memory-leak-debug

Bug 2131

See bug 3681 comment 16

Follow on to commit 79ff60f4.

Bug 3681

Bug 3776

KNL modes if not KNL system.

Bug 3825

This reverts commit c2380520.

KNL modes if not KNL system.

Bug 3825

reconfigured while node boot in progress.

Bug 3679

bug 3822

Bug 3708

Bug 3815

not being able to deal with pn_min_memory being a uint64_t.  Scripts are
urged to change to these new variables avoid issue.  If not set the
variables will be 'nil'.

Bug 3681

In 17.11(or other future version) we should move a lot of this common
code into a new lib.  The reason I didn't put these common changes
into common/xlua.c was because then I would have to link common to
liblua which I really didn't want to do.

dependencies.

Bug 3708

Bug 3772

are ready.  This will be NULL is a job was revoked while beginning.

allocation has been revoked as it was beginning.

if there was a failure after the initial resource allocation. Does not
release previously allocated resources.

Bug 3783

This is the initial patch that adds the stubs for the logic.  Outside of
that this patch really does nothing.

configured.

fails to enter the desired NUMA and/or MCDRAM mode then drain the node and
requeue the job.

Bug 3785

prolog is ran after the reboot.

Bug 3618

Precursor for next commit.

Bug 3618

Bug 3695

bug 3779

If capmc reports a node name, but not mcdram_cfg for the node, then
  log the missing data rather than assume the value is zero and
  report a value mismatch with cnselect.

When requesting an operation on jobs, where the operation permits to specify
more than one job in the same request, and a job array appears before a
regular job (no-array job) in the list of jobs to operate with, the
job_array_resp_msg_t pointer was not properly NULL'ed and thus incorrectly
accessed when processing the no-array job. This fix prevents the crash from
happening in the following scontrol operations:

uhold, hold, suspend, requeue, requeuehold, update, release

when the same request has <array_jobid>,<non-array_jobid> in this order in
the job list to process.

Bug 3759

Job expansion example in FAQ enhanced to demonstrate operation in
    heterogeneous environments.
bug 2979

Do not attempt to schedule jobs after changing the power cap if there are
    already many active threads.