-
Notifications
You must be signed in to change notification settings - Fork 67
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
Question about MPI_Finalize #535
Comments
Hi @ollielo, thanks for the report. Caliper should still trigger a flush on MPI_Finalize() itself. What's your runtime configuration? It looks like you're manually configuring Caliper with |
Thanks for your answer. I was kind of getting it reversed. Previously, we did not need to explicit shutdown Caliper and it seemed like Caliper will intercept our call to
before we calling
|
Caliper should still intercept the MPI_Finalize() call. If you're configuring Caliper with By default we're using the GOTCHA library which comes with Caliper to intercept MPI calls. It explicitly intercepts the C API Finally, calling |
I tried what you suggested. Here is the relevant part of the log
It looks to me that both |
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 likeDo we now have to call MPI_Finalize ourself?
The text was updated successfully, but these errors were encountered: