slurmd yet delivering it's TRES list.

Bug 6122

Co-authored-by: Marshall Garey <marshall@schedmd.com>

Bug 6008

then an error is generated if more than one of those specifications
contains KNL NUMA or MCDRAM modes.

Bug 5846

Bug 5846

are down nodes.

Bug 5846

NODE_SET_REBOOT to continue.

Bug 5846

node change when possible.

Bug 5846

Break out a list of Linux distributions as well.

Plugins reading in their own config files rely on the SLURM_CONF
environment variable pointing to the appropriate directory,
otherwise they will fall back to the build in sysconfdir path.

Set the environment variable early enough so that the -f flag
operates correctly, but not before conf->conffile has definitely
been set. Remove the setenv call that happens before the first
slurmstepd is fork()'d as it is now redundant.

Bug 4774.

sbatch sets these, but salloc did not. This should make srun behavior
between the two consistent.

Bug 3861.

time that wasn't existent instead of just updating lines that have time
with a lesser time.

Slurm is going to replace internally.

Bug 5800

Bug 6121

Bug 6008

Bug 6077

node system.

Bug 6037

Bug 6037

Bug 5983

In case of the error code paths (like collective timeout) it is possible
that a callback provided by PMIx will be called twice leading to a
segmentation fault.
This commit fixes it by properly accounting callback invocations.

Bug 5983

This reverts commit b0515009.

Bug 5935

This could have caused core dumps if communication failed for one
reason or another.

Signed-off-by: Boris Karasev <karasev.b@gmail.com>

Bug 5935

In case of the error code paths (like collective timeout) it is possible
that a callback provided by PMIx will be called twice leading to a
segmentation fault.
This commit fixes it by properly accounting callback invocations.

This patch does 2 things:
1. When a step fails on some node, then mark it as complete on those
   nodes. This is needed so that when the step ends on the other
   nodes, slurmctld recognized the step as completely done.
2. If the step does not have the --no-kill option set, then when some
   node fails, send a request to terminate the step on ALL of its nodes.

Bug 5805

Bug 5977

Removed in 19.05 release; remove the documentation in 18.08 to
discourage further use.

Bug 6075.

when env is overwritten by the command line.

Bug 5977

Bug 6016

Bug 6092

configuration.

Bug 5872

canceled while pending.

Bug 6016

Bug 6015.

Was attributed to the wrong author by mistake.

This reverts commit 8b5acf90.

Explain gotchas with --export when an implicit --get-user-env is
triggered.
Correct example in the docs; `--export=EDITOR,ALL` does not make any
sense.
Explain how env vars are propagated with srun and sbatch when `ALL` is
specified; document their differences.
Explain that srun --export is implemented in the Launch plugin.
Fix minor grammatical errors.
Remove --export reference in salloc.

Bug 6042

Each nested <ul> needs to be within an <li>. And add in one missing </ul>.