Aha - I found it. It’s a typo in the v2.2.1 release. Sadly, our Slurm plugin
folks seem to be off somewhere for awhile and haven’t been testing it. Sigh.
I’ll patch the branch and let you know - we’d appreciate the feedback.
Ralph
> On Jan 18, 2019, at 2:09 PM, Michael Di Domenico
> wrote:
>
here's the branches i'm using. i did a git clone on the repo's and
then a git checkout
[ec2-user@labhead bin]$ cd /hpc/src/pmix/
[ec2-user@labhead pmix]$ git branch
master
* v2.2
[ec2-user@labhead pmix]$ cd ../slurm/
[ec2-user@labhead slurm]$ git branch
* (detached from origin/slurm-18.08)
ma
Looks strange. I’m pretty sure Mellanox didn’t implement the event notification
system in the Slurm plugin, but you should only be trying to call it if OMPI is
registering a system-level event code - which OMPI 3.1 definitely doesn’t do.
If you are using PMIx v2.2.0, then please note that there
i compilied pmix slurm openmpi
---pmix
./configure --prefix=/hpc/pmix/2.2 --with-munge=/hpc/munge/0.5.13
--disable-debug
---slurm
./configure --prefix=/hpc/slurm/18.08 --with-munge=/hpc/munge/0.5.13
--with-pmix=/hpc/pmix/2.2
---openmpi
./configure --prefix=/hpc/ompi/3.1 --with-hwloc=external
--wit
