Skip to content

prrte submodule pointer bump broke --report-bindings #12143

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

Closed
wenduwan opened this issue Dec 1, 2023 · 5 comments
Closed

prrte submodule pointer bump broke --report-bindings #12143

wenduwan opened this issue Dec 1, 2023 · 5 comments

Comments

@wenduwan
Copy link
Contributor

wenduwan commented Dec 1, 2023

Background information

What version of Open MPI are you using? (e.g., v3.0.5, v4.0.2, git branch name and hash, etc.)

main and v5.0.x

Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)

Build from source

If you are building/installing from a git clone, please copy-n-paste the output from git submodule status.

 9095457b2c5b2370178a9a0ffaff7a6918af632e 3rd-party/openpmix (v1.1.3-3932-g9095457b)
 066b56055c4f9017a581dc472864c9e2d8c189cc 3rd-party/prrte (psrvr-v2.0.0rc1-4706-g066b56055c)
 c1cfc910d92af43f8c27807a9a84c9c13f4fbc65 config/oac (heads/main)

Please describe the system on which you are running

  • Operating system/version: Amazon Linux 2
  • Computer hardware: EC2
  • Network type: EFA

Details of the problem

We recently bumped prrte submodule pointer in main and v5.0.x branch. After this, mpirun --report-bindings ... segfaults

@wenduwan
Copy link
Contributor Author

wenduwan commented Dec 4, 2023

The issue is fixed in openpmix/prrte#1878

Now we need to bump prrte pointer in both main and v5.0.x

I'm ok with doing that on main, but v5.0.0x needs a release tag soon(like on 12/8).

@wenduwan
Copy link
Contributor Author

wenduwan commented Dec 7, 2023

Hey @rhc54, we are about to start 5.0.1 RC process - we would like to ingest a new prrte release or RC with the known bugfixes. Could you provide an ETA for that?

@rhc54
Copy link
Contributor

rhc54 commented Dec 7, 2023

Should be done this evening.

@wenduwan
Copy link
Contributor Author

wenduwan commented Dec 8, 2023

@rhc54 Thank you very much!

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