Question about MPI_Finalize
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 420
- Forks
- 80
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 9
Description
We are using the `Annotation` interface in our code. We used to (in pre-2.10) be able to rely on the destroctor or some other Caliper internal mechanism to call MPI_Finalize before Caliper is shut down. However, in 2.10, we got something like
```
== CALIPER: default: mpireport: MPI is already finalized. Cannot aggregate output
```
Do we now have to call MPI_Finalize ourself?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start with the Annotation interface and the MPI_Finalize/Caliper shutdown path, then reproduce the mpireport diagnostic. Done means establishing whether Caliper should finalize MPI and documenting or correcting that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100