Why would it not be set? AFAICT, Slurm is supposed to always set that envar, or so we've been told.
On Mar 12, 2021, at 2:15 AM, Martyn Foster via devel <devel@lists.open-mpi.org <mailto:devel@lists.open-mpi.org> > wrote: Hi Ralph, Slurm is 19.05. To be clear - its not unexpected that SLURM_TASKS_PER_NODE is unset in the configuration. Martyn On Thu, 11 Mar 2021 at 16:09, Ralph Castain via devel <devel@lists.open-mpi.org <mailto:devel@lists.open-mpi.org> > wrote: What version of Slurm is this? > On Mar 11, 2021, at 8:03 AM, Martyn Foster via devel > <devel@lists.open-mpi.org <mailto:devel@lists.open-mpi.org> > wrote: > > Hi all, > > Using a rather trivial example > mpirun -np 1 -rf rankfile ./HelloWorld > on a Slurm system; > -------------------------------------------------------------------------- > While trying to determine what resources are available, the SLURM > resource allocator expects to find the following environment variables: > > SLURM_NODELIST > SLURM_TASKS_PER_NODE > > However, it was unable to find the following environment variable: > > SLURM_TASKS_PER_NODE > > -------------------------------------------------------------------------- > > (Both for OpenMPI 4.0/4.1). It is correct the variable is not set, but why > is SLURM_TASKS_PER_NODE expected or required when using a rankfile where one > presumes it would not be a constant across the job anyway? > > Martyn >
