-
Notifications
You must be signed in to change notification settings - Fork 885
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
v5.0.x: Propagate the error up to the user. #12253
base: v5.0.x
Are you sure you want to change the base?
Conversation
@jsquyres I run this PR: https://github.com/mpi4py/mpi4py-testing/actions/runs/7588222142/job/20670268020
PS: For reference, this test is passing with MPICH, but that's simply because of their implementation choices. |
I'll perform a new test today with ompi@main, I'm not convinced the current behavior is the right one (not that my opinion matters, of course). |
@dalcinl Did you get a chance to do a test, our goal was to get an rc out today. |
Thanks - let me discuss with RMs, thank you very much for the reproducers! |
Make sure to reset the generalized request to guarantee not to call the free callback a second time. Signed-off-by: George Bosilca <bosilca@icl.utk.edu> (cherry picked from commit ac3647e)
ac271d3
to
7c1a10a
Compare
Now that @hppritcha has added mpi4py for v5.0.x, I rebased this PR and will check CI result. I assume it's safe to merge if CI passes. |
Make sure to reset the generalized request to guarantee not to call the free callback a second time.
Signed-off-by: George Bosilca bosilca@icl.utk.edu
(cherry picked from commit ac3647e)
This is the v5.0.x PR corresponding to main PR #11683
Refs #11681.
FYI @dalcinl