- Notifications
You must be signed in to change notification settings - Fork 928
pmix/pmix112: Update to version 1.2.0 #2286
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
Conversation
| Note that there is nothing to cherry-pick from OMPI |
| @karasevb, please verify that this is working well. |
| FWIW: I have MTT running it now on my cluster - so far, so good. Will post results when done |
a6e4935 to 708dfc6 Compare | Using the internal version things are looking good. I'm looking into some include issue with the |
| No problems found with the internal version: |
| It works well. And checked with external. |
| PMIx 1.2.0rc1 is here (in case folks want to try it with the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a Signed-off-by line to this PR's commits.
1ff5080 to a6a6ff1 Compare Commit message has been updated with sign-off
| bot:ibm:retest |
a6a6ff1 to a180bc5 Compare a180bc5 to 59b2b63 Compare 59b2b63 to 3bf8426 Compare 3bf8426 to 1accd06 Compare | I just updated this branch with the v1.2.0rc2: |
Thanks to Kevin Buckley for pointing it out (cherry picked from commit 0b3f4c5) Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
* This attempts to match the current state on OMPI `master`, however those commits do not cleanly cherry-pick over so we created a custom patch for the changes noted below: - open-mpi/ompi@9a5ef60 - open-mpi/ompi@55923ea - open-mpi/ompi@7b115a9 - open-mpi/ompi@12ecf97 - open-mpi/ompi@639dbdb - open-mpi/ompi@af67f16 Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
1accd06 to abf7378 Compare | I just pushed an updated version that matches the PMIx v1.2.0 release. |
| @rhc54 If you have a chance can you review this branch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work fine
| Per discussion on the OMPI teleconf: We might want to wait on pulling this in until we get the PMIx v1.2.1 point release. Alternatively, we could merge this in and I can create another PR for the PMIx v1.2.1 update. Whichever the RMs decide would be better. |
| @jjhursey I think it doesn't matter because the end date is going to be the same in both cases, right? If that's correct, do whichever one is less work. 😄 |
| It's probably less work to just update this PR with an additional commit once PMIx v1.2.1 is released. I guess the only reason to merge it in sooner would be to get more MTT testing on it. |
| Discussion on the OMPI Teleconf. Let's merge this in to get some MTT exposure. I'll open another PR once PMIx v1.2.1 is ready. PMIx v1.2.1 will be a bug fix release. |
Uh oh!
There was an error while loading. Please reload this page.