Skip to content
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

PMIx/v2.1 mca/ptl early release bug #4830

Closed
artpol84 opened this issue Feb 18, 2018 · 8 comments
Closed

PMIx/v2.1 mca/ptl early release bug #4830

artpol84 opened this issue Feb 18, 2018 · 8 comments

Comments

@artpol84
Copy link
Contributor

Open it here to keep track.
@bwbarrett @jsquyres @jjhursey @jladd-mlnx this is a blocker for v3.1 - we observed the issue with OMPI v3.1 testing.
The fix is pending the check/review in PMIx/master (openpmix/openpmix#673), will need to port it to PMIx/v2.1 and bring it here.

@artpol84
Copy link
Contributor Author

PMIx/master PR is merged.
v2.1 is filed: openpmix/openpmix#674

@artpol84
Copy link
Contributor Author

PMIx/v2.1 PR is merged so PMIx side is fixed.
@bwbarrett @jsquyres what is the preferred way to bring this into OMPI v3.1? Port the commit or create a huge PR similar to #4746?

@rhc54
Copy link
Contributor

rhc54 commented Feb 18, 2018

Huge PR??? There aren't very many changes in going from PMIx v2.1.0 to v2.1.1 - so why would this be "huge"?

@artpol84
Copy link
Contributor Author

@rhc54 What I was asking is: do we want to do another sync or we want to port this specific fix.
My impression was that we are trying to release OMPI v3.1 ASAP and may not want to wait until PMIx v2.1.1 will be released.
It seems like you suggest to do another sync. I am fine with this.

@rhc54
Copy link
Contributor

rhc54 commented Feb 18, 2018

Yeah, I think they would be better off as there were a few bugs found since we released v2.1.0 - might as well sweep them all up. However, it is up to them. I just wanted to clarify that it shouldn't be a large amount of change, which is what your earlier comment implied.

@artpol84
Copy link
Contributor Author

Thank you for the information @rhc54.

@artpol84
Copy link
Contributor Author

Sync v2.1:
#4831

@artpol84
Copy link
Contributor Author

Fix is in v3.1.x, issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants