an MPI problem caused a test failure for me and since it's not running
an MPI job, just disable the MPI plugin

CID 198639

Continuation of 8a1e5a52

Bug 6950

Mostly in copywrite notices, but some comments and documents also.
bug 7090

Bug 7092.

Can happen if SrunPortRange has been set too small, especially on shared
login nodes launching multiple large-scale srun processes.

Bug 6916

Bug 6995

Bug 6467

Job steps that run on cloud nodes and use the alias_list - in other
words, SlurmctldParameters=cloud_dns is not in slurm.conf - all talk
directly back to the slurmctld. To make that happen, we set the parent
tank of each stepd to -1. However, we also set the rank of each stepd to
0. this meant that when each stepd sent a REQUEST_STEP_COMPLETE RPC to
the slurmctld, they would tell slurmctld to clean up node 0 in the step
allocation. So, multi-node step allocations weren't cleaning up after
the steps completed and would cause subsequent job steps to hang. The
step allocations would only clean up properly at the end of the job.

Ensure that each stepd uses the correct rank so that job steps are
properly cleaned up after each step completes.

Bug 6467.

They were associated to these two commits:

b4d7de48
6871185a

Bug 5562.

They were associated to these two commits:

b4d7de48
6871185a

Bug 5562.

Bug 6998.

Modify "scontrol show dwstat" test to work if no active sessions,
configurations, etc.

Correct some logic in commit 38daa7a9. The variable "file_in"
did not exist in some places where the function was called from.

Modify test to work on cray/kachina system when allocated KNL node.

Test broke on cray/kachina when allocated KNL

Bug 6822

Bug 7061

Bug 7061

Bug 7061

Co-authored-by: Morris Jette <jette@schedmd.com>

Error reported by CLANG

Cherry pick to 18.08.

Bug 6996.

Jobs with zero nodes/CPUs are permitted to create and destroy
persistent burst buffers.

Bug 7034.

Bug 7034.

unlimited could get overwritten with default queue depth preventing the
whole queue from being looked at -- especially in a high-throughput
envrionment.

Bug 6822

Co-authored-by: Morris Jette <jette@schedmd.com>

Bug 5562

Bug 5562

Bug 5562

Node memory overallocation wouldn't be properly detected since we would
just be interpreting the available memory as RealMemory - MemSpecLimit,
ignoring other job's memory usage.

Bug 5562.

This compares a job memory request against each selected node available
memory, interpreting the latter for now as RealMemory - MemSpecLimit.

Bug 5562.

Place all three memory cases (per cpu, per node and all node memory) in
a single loop, since all three cases need to traverse all job_resources
selected nodes. Preparation for a follow-up commit that contains the
real fix.

Bug 5562.

Move common (or similar) logic to globals and remove it from
the individual tests.

Add handling for acct_gather_energy/xcc and acct_gather_profile/influxdb.

Bug 6829.