Skip to content

Fix singleton operations when running under a SLURM allocation. #1037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 19, 2015
Merged

Fix singleton operations when running under a SLURM allocation. #1037

merged 1 commit into from
Oct 19, 2015

Conversation

rhc54
Copy link
Contributor

@rhc54 rhc54 commented Oct 18, 2015

Sadly, SLURM's PMI will return success even if the PMI server isn't actually available. This leads to erroneous selection of pmix and ess components. So add a further requirement (namely, that we see a job_step envar) to the SLURM pmix components along with some modification of ess selection code to avoid the problem

…, SLURM's PMI will return success even if the PMI server isn't actually available. This leads to erroneous selection of pmix and ess components. So add a further requirement (namely, that we see a job_step envar) to the SLURM pmix components along with some modification of ess selection code to avoid the problem
@rhc54 rhc54 added the bug label Oct 18, 2015
@rhc54 rhc54 added this to the Open MPI v2.0.0 milestone Oct 18, 2015
@igor-ivanov
Copy link
Member

Checked. It is OK.

igor-ivanov added a commit that referenced this pull request Oct 19, 2015
Fix singleton operations when running under a SLURM allocation.
@igor-ivanov igor-ivanov merged commit 71ec545 into open-mpi:master Oct 19, 2015
@rhc54 rhc54 deleted the topic/singleton branch October 23, 2015 19:28
jsquyres pushed a commit to jsquyres/ompi that referenced this pull request Aug 23, 2016
…rndv

MTL portals4 : fix around triggered rndv operations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants