v3.1.x: plm_slurm_module: adjust for new SLURM CLI options #6673
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SLURM 19 discontinued the use of --cpu_bind (and changed it to
--cpu-bind). There's no easy way to test at run time which one is
accepted, so set the environment variable SLURM_CPU_BIND to "none",
which should do the same thing as the srun CLI parameter.
Signed-off-by: Jordan Hayes [email protected]
Signed-off-by: Jeff Squyres [email protected]
(cherry picked from commit 7dad740)
FYI @jdhayes
Release managers: I marked this as "NEWS" because this commit fixes the SLURM plm (for
mpirun-based launching, not native launch/srun-based launching) with regard to SLURM 19, because SLURM 19 deleted a CLI option that previous versions of Open MPI were using. This PR works around the issue by using a SLURM env var instead of the problematic CLI option. This env var works with really old versions of SLURM (we checked back to SLURM 14) up to SLURM 19.