Like this?

[Joe-Downs]

Please submit all the information below so that we can understand the working environment that is the context for your question.

• If you have a problem building or installing Open MPI, be sure to read this.
• If you have a problem launching MPI or OpenSHMEM applications, be sure to read this.
• If you have a problem running MPI or OpenSHMEM applications (i.e., after launching them), be sure to read this.

Background information

What version of Open MPI are you using? (e.g., v4.1.6, v5.0.1, git branch name and hash, etc.)

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

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

Please describe the system on which you are running

• Operating system/version:
• Computer hardware:
• Network type:

---

Details of the problem

Please describe, in detail, the problem that you are having, including the behavior you expect to see, the actual behavior that you are seeing, steps to reproduce the problem, etc. It is most helpful if you can attach a small program that a developer can use to reproduce your problem.

Note: If you include verbatim output (or a code block), please use a GitHub Markdown code block like below:

shell$ mpirun -n 2 ./hello_world

[jsquyres]

Thanks. Let's make sure the "remove needs-reply" bot still works...

[Joe-Downs]

Add your comment here...

[jsquyres]

Cool; I didn't break it. 😄 Let's let this issue go stale overnight, and get closed another day later...

[github-actions]

It looks like this issue is expecting a response, but hasn't gotten one yet. If there are no responses in the next XYZ days, we'll assume that the issue has been abondoned and will close it.

[Joe-Downs]

Leave a comment

[jsquyres]

Thanks. Let's see if we got the action logic correct this time; re-added the needs-reply label. That should make this go stale and then auto-close.

[github-actions]

It looks like this issue is expecting a response, but hasn't gotten one yet. If there are no responses in the next XYZ days, we'll assume that the issue has been abondoned and will close it.

[github-actions]

Per the above comment, it

I'm going to close this issue. If I'm wrong and this issue is not abondoned, please feel free to re-open it. Thank you!