Skip to content

Conversation

@jjhursey
Copy link
Member

No description provided.

Signed-off-by: Joshua Hursey <[email protected]>
@rhc54
Copy link
Contributor

rhc54 commented Mar 29, 2018

whistle...wow, that's a big amount of change, dude! Are the RMs going to accept this?

@jjhursey
Copy link
Member Author

They are using PMIx 2.0.1rc1 right now. If they want cross version support in v3.0.1 then it should be considered. I'll leave it to the RMs.
It's worth considering, thus the PR. But it might be wise to push to v3.0.2 (with a quick turn around) so that it gets some testing.

PMIX_INFO_CREATE(info, ninfo);
cnt=ninfo;
if (PMIX_SUCCESS != (rc = pmix_bfrop.unpack(buf, info, &cnt, PMIX_INFO))) {
if (0 < cd->ninfo) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jjhursey I recvd a request that we always provide the PMIX_PARENT_ID and PMIX_SPAWNED attributes when a client proc (but not a tool) dynamically starts another job. See the code now in master - might be an idea to backport it here for consistency.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: my "changes request" relates solely to the above comment. Otherwise, things look fine to me, so I'll change my review to "approved" as the above is optional and up to @jjhursey .

@rhc54
Copy link
Contributor

rhc54 commented Mar 29, 2018

@hppritcha @jsquyres Just to clarify (since I commented about the size of this PR) - much of the changes consist of mods to copyrights and removal of some files. Of the remaining changes, they fall into three categories:

  1. bug fixes that impact correctness and cross-version support
  2. better isolation of the PMI-1/2 backward compatibility libraries, which OMPI doesn't build
  3. changes to non-executing files such as the rpm spec file

The first category is the smallest of the group, and so I'd recommend moving ahead with it (precise timing is up to you).

@jsquyres jsquyres changed the title Update to PMIx 2.0.3 v3.0.x: Update to PMIx 2.0.3 Mar 29, 2018
@bwbarrett
Copy link
Member

After some discussion, since Open MPI 3.0.1 is all but released (all that's left is the web page update), we're going to release 3.0.1 without this patch and ship it with 3.0.2, targetted for 1 month out.

@bwbarrett bwbarrett modified the milestones: v3.0.1, v3.0.2 Mar 29, 2018
@bwbarrett bwbarrett merged commit e8cec80 into open-mpi:v3.0.x Mar 29, 2018
@jjhursey jjhursey deleted the update/v3.0.x-to-pmix-2.0.3 branch March 29, 2018 16:40
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.

4 participants