Bug 6155

Bug 6155

When bf_continue is set, and locks are released during a backfill cycle,
other operations can make new resorces available while part way through
the queue. When backfill continues the cycle and evaluates new jobs, it
may allocate some of these newly available resources to lower priority jobs,
rather than to higher priority jobs that were already considered in this
backfill cycle.

This patch introduces bf_ignore_newly_avail_nodes to SchedulerParameters
to solve this issue. This option will ignore nodes made available when
the backfill scheduler yields when resuming the backfill cycle.

Bug 5279.

slurmd yet delivering it's TRES list.

Bug 6122

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

Bug 6008

Bug 6008

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

Bug 5846

are down nodes.

Bug 5846

NODE_SET_REBOOT to continue.

Bug 5846

node change when possible.

Bug 5846

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

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

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

when env is overwritten by the command line.

Bug 5977

Bug 6016

Bug 6092

configuration.

Bug 5872

Bug 6015.

Was attributed to the wrong author by mistake.

This reverts commit 8b5acf90.

Add support for SALLOC/SBATCH/SLURM_NO_KILL environment variables.
Add salloc/sbatch/srun support for optional "--no-kill=off" option to
disable the environment variables.
Needed for a USGS procurement.

Bug 5977

started on a node.

Bug 5865

Bug 6061

bug 6016

Bug 6015

Bug 6015

Bug 4961.

The srun man page states that --prolog=none or --epilog=none would
prevent the SrunProlog or SrunEpilog scripts defined in slurm.conf from
running. However, with SLURM_TEST_EXEC set in the environment, srun
would look for a script named "none" and run it if found. If not found,
then srun would print an error message, but the SrunProlog or
SrunEpilog would (correctly) not run.

* Prevent srun from running a script named "none" that is in the path.
* This also prevents the error message if it is not found.

Bug 5948.