ifficult beast to interface
> with, and I have yet to find a single, reliable marker across the various
> slurm releases to detect options we cannot support.
>
>
> On Jul 7, 2010, at 11:59 AM, David Roundy wrote:
>
>> On Wed, Jul 7, 2010 at 10:26 AM, Ralph Castain wrote:
&
On Wed, Jul 7, 2010 at 10:26 AM, Ralph Castain wrote:
> I'm afraid the bottom line is that OMPI simply doesn't support core-level
> allocations. I tried it on a slurm machine available to me, using our devel
> trunk as well as 1.4, with the same results.
>
> Not sure why you are trying to run th
On Tue, Jul 6, 2010 at 12:31 PM, Ralph Castain wrote:
> Thanks - that helps.
>
> As you note, the issue is that OMPI doesn't support the core-level allocation
> options of slurm - never has, probably never will. What I found interesting,
> though, was that your envars don't anywhere indicate tha
;
>
> On Jul 6, 2010, at 12:16 PM, David Roundy wrote:
>
>> Hi all,
>>
>> I'm running into trouble running an openmpi job under slurm. I
>> imagine the trouble may be in my slurm configuration, but since the
>> error itself involves mpirun crashing, I thoug
For what it's worth, the slurm environment variables are:
SLURM_JOBID=2817
SLURM_JOB_NUM_NODES=1
SLURM_TASKS_PER_NODE=1
SLURM_TOPOLOGY_ADDR_PATTERN=node
SLURM_PRIO_PROCESS=0
SLURM_JOB_CPUS_PER_NODE=2
SLURM_JOB_NAME=submit.sh
SLURM_PROCID=0
SLURM_CPUS_ON_NODE=2
SLURM_NODELIST=node02
SLURM_NNODES=1
slurm config (or anything else that seems useful)
if you think that would be helpful!
--
David Roundy
