Skip to content

Conversation

@rhc54
Copy link
Contributor

@rhc54 rhc54 commented Aug 20, 2018

Signed-off-by: Ralph Castain [email protected]

Signed-off-by: Ralph Castain <[email protected]>
@rhc54 rhc54 added the bug label Aug 20, 2018
@rhc54 rhc54 added this to the v3.1.2 milestone Aug 20, 2018
@rhc54 rhc54 self-assigned this Aug 20, 2018
@rhc54 rhc54 requested a review from jjhursey August 20, 2018 19:14
@ggouaillardet
Copy link
Contributor

I think we should address openpmix/openpmix#817 and then upgrade to PMIx 2.1.4 (or backport the fix)

@jsquyres
Copy link
Member

Per 2018-08-21 webex, @rhc54 says that this is not a blocker for release. It's a bug that occurs during PMIx notifications, and the only time OMPI uses those is when something else is already going wrong (i.e., error notifications). It would be good to fix, but it's not a blocker.

@bwbarrett bwbarrett modified the milestones: v3.1.2, v3.1.3 Aug 22, 2018
@jsquyres
Copy link
Member

@rhc54 I think that this is worthwhile: we want well-behaved error paths. So if we can upgrade to pmix 2.1.4 (per @ggouaillardet's comment), that would be great.

@jjhursey
Copy link
Member

IT sounds like we are holding this one until we get a PMIx patch on top of 2.1.3, right?

@rhc54
Copy link
Contributor Author

rhc54 commented Aug 29, 2018

No, we are holding until PMIx release 2.1.4 and then will update this PR

@rhc54
Copy link
Contributor Author

rhc54 commented Sep 12, 2018

Replaced by #5690

@rhc54 rhc54 closed this Sep 12, 2018
@rhc54 rhc54 deleted the cmr31/pmix213 branch September 12, 2018 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants