This is not working reliably even when setting
SchedulerParameters=enable_hetero_steps and/or using OpenMPI with Slurm's
mpi/pmi2, as it was previously documented.

Bug 5309.

Documented, and code reads as needing, the node lock. But these
were incorrectly set as the job locks.

Bug 5394.

Needs the job write lock, as it may change job status not just node
status. Especially after commit 33e352a6.

Bug 5406.

Previously, usage was just CPU-seconds. However, since
TresBillingWeights has been added, usage gets calculated from that, or
it's just CPU-seconds if TresBillingWeights isn't defined.

Bug 5434.

Add errno to info message in the SlurmDBD log, and pass the actual
errno back to the sacctmgr process so the user can see it.

Bug 5152.

- avoid `abort()` when collective is failed
- added logging of coll details for fail cases

Bug 5067

Note, this is setting it up so we can use defunct functions.  It will
probably need to be properly fixed in a future version so we don't
do this.

Bug 5098.

with preemption or when job requests a specific list of hosts.

Bug 5293.

Bug 5395

Bug 5390

Continuation of 923c9b37.

There is a delay in the cgroup system when moving a PID from one cgroup
to another. It is usually short, but if we don't wait for the PID to
move before removing cgroup directories the PID previously belonged to,
we could leak cgroups. This was previously fixed in the cpuset and
devices subsystems. This uses the same logic to fix the freezer
subsystem.

Bug 5082.

cpuset and devices subsystems have duplicate code to cleanup the cgroup
and prevent leaking cgroups by moving the process to the root cgroup and
waiting for it to be moved.

Move this duplicate code to a common function so it can be used later by
the freezer subsystem.

Bug 5082.

Bug 5227

bug4451

So that multiple nodes changes will be reported on one line rather than one
line per node. Otherwise this could lead to performance issues when reloading
slurmctld in big systems.

Bug4980

Slurm numbers the cores using an abstract index, starting from CPU 0
on the first socket, core, thread, and continuing until N on the last socket,
last core, last thread. Explain that in the documentation.

bug 5189

Currently, no caller checks the return code.

Bug 5164

Can't have # character in the password since it is treated as a comment.

Bug 5294

Only produces a whitespace difference in configure. Inadvertently
introduced by commit 103ebaac.

Bug 5335.

Firefox handles flex differently than Chrome. When flex is set to 1,
the flex item does not respect the flex container's bounds, causing
text to be cutoff.

Bug 5339.

Some job fields can change in the course of scheduling. This patch
reinitializes previously adjusted job fields to their original value
when validating the job memory in multi-partition requests.

Bug 4895.

This reverts commit bf4cb0b1.

Bug 5240, Bug 4895 and Bug 4976.

When one asks for an inactive feature and also specifies the node with -w flag,
the node will be rebooted despite it may contain running jobs.

bug4821

and avoid race condition calling task before proctrack can introduce.

Bug 5319

to work correctly.

Bug 5155
Bug 4516

delayed until the first job completes execution and it's burst buffer
stage-out is completed.

Bug 4675

Bug 5191

Bug 5159.

MUNGE plugin is no longer packaged separate after the slurm.spec overhaul.

Enhancements to commit 35a13703
bug 5185

Enhancements to commit 35a13703
bug 5185

Previously the function was only testing against the first partition in
the job_record. Now it detects if the job request is multi partition and
if so then loops through all of them until the job will run in any or
until the end of the list, returning the error code from the last one if
the job won't run in any partition.

Bug 5185

This can happen if burst buffer logic is broken

When requesting specific jobids with sacct, the starttime of the request
is 0, which will cause the time range to be outside of the
MaxQueryTimeRange range -- if specified. When requesting specific
jobids, sacct should be able to find the job whenever it started --
unless confined to a smaller range with -S and/or -E.

Bug 5009

Specifically due to SELECT ... FOR UPDATE ones.

Bug 5086.