Skip to content

Conversation

@hppritcha
Copy link
Member

the upping of age and rev for libmpi.so/libmpif owes
to additions to the mpi.h and mpif.h include files.

[ci skip]

Signed-off-by: Howard Pritchard [email protected]

Copy link
Member

@jsquyres jsquyres left a comment

Choose a reason for hiding this comment

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

@hppritcha Given the comments I made, I'm not sure we're looking at the same commit range on the v2.x branch. Can you verify that I'm looking at the right range of commits?

VERSION Outdated
# format.

libmpi_so_version=30:0:10
libmpi_so_version=31:0:11
Copy link
Member

Choose a reason for hiding this comment

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

I agree with the libmpifh version change, but I do not see an mpi.h change that would cause this libmpi_so_version change. I'm looking on the v2.x branch starting with the 62cd194 commit. Are we looking at the same commit range?

Copy link
Member

Choose a reason for hiding this comment

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

Ok, I guess I shouldn't be using --no-merge in my git log.

So I now see fda9157 that modified mpi.h. But it just added a #define -- it didn't add any interfaces. So I don't think we should be bumping to 31:0:11, but rather to 30:1:10.

Copy link
Member Author

Choose a reason for hiding this comment

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

libmpi.so got bumped by fda9157 which was merged in by 4b6d34a (PR #3138)

libopen_pal_so_version=30:1:10
libmpi_java_so_version=30:0:10
liboshmem_so_version=30:0:10
liboshmem_so_version=30:1:10
Copy link
Member

Choose a reason for hiding this comment

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

I didn't see any OSHMEM changes on v2.x after 62cd194. Did I miss them?

Copy link
Member

Choose a reason for hiding this comment

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

Ok, I see the oshmem change now.

libmca_opal_common_cuda_so_version=30:0:10
libmca_opal_common_libfabric_so_version=30:0:10
libmca_opal_common_sm_so_version=30:0:10
libmca_opal_common_sm_so_version=30:1:10
Copy link
Member

Choose a reason for hiding this comment

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

I also didn't see any opal/mca/common/sm changes on v2.x after 62cd194.

Copy link
Member

Choose a reason for hiding this comment

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

And I see the common/sm change now.

Copy link
Member Author

Choose a reason for hiding this comment

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

commit 2379e6e which was merged in by 97c95c4 as part of #3189

@hppritcha
Copy link
Member Author

I got the list of changed files by checking out v2.x in my repo and then doing

git diff --name-only 1cd1edf..HEAD

the sha is that for the v2.1.0 tag

@hppritcha
Copy link
Member Author

Sorry typed the sha wrong. Typing on my iphone

@hppritcha
Copy link
Member Author

What got command are you using? The pvar sessions thing got merged in as 3139. hmmm that was the thing I missed in the readme.

@jsquyres
Copy link
Member

Looks like I started 1 commit after you, and that didn't really affect any noticeable change.

I just checked out the v2.x head and ran git log --stat --no-merges > log.txt. I then opened the file in emacs, went down to 62cd194, and trimmed everything after that.

@hppritcha
Copy link
Member Author

i dont think your command is the right one.

@hppritcha
Copy link
Member Author

Problem is that things like the mpi.h.in change was only merged in a few weeks ago.

@hppritcha
Copy link
Member Author

#3139 pulled that change in. I merged Omir's commit on 3/29.

@hppritcha
Copy link
Member Author

same kind of mistake with the sm common. The change was actually merged in by #3189 which got merged in by me on 3/28.

@hppritcha
Copy link
Member Author

hppritcha commented Apr 27, 2017

Oh I noticed I had updated NEWS with #3139 info. Just forgot to delete the reminder line. So the README should be ready to go.

@jsquyres
Copy link
Member

Only thing left now is the version for libmpi.

@hppritcha
Copy link
Member Author

Your git command is defective for finding changes between releases, at least within a given branch. I'll update the release checklist.

the upping of age and rev for libmpi.so/libmpif owes
to additions to the mpi.h and mpif.h include files.

[ci skip]

Signed-off-by: Howard Pritchard <[email protected]>
@hppritcha hppritcha force-pushed the version_update_v2.1.1 branch from 4fb1b44 to 3c5254d Compare April 27, 2017 16:10
Copy link
Member

@jsquyres jsquyres left a comment

Choose a reason for hiding this comment

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

@hppritcha and I talked in IM and figured it all out. We agree that the values are good now.

@jsquyres jsquyres merged commit 991cd22 into open-mpi:v2.x Apr 27, 2017
@hppritcha hppritcha deleted the version_update_v2.1.1 branch May 2, 2018 03:00
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.

2 participants