-
Notifications
You must be signed in to change notification settings - Fork 286
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
spawn: better error handling when connection time out #5816
Conversation
933ae45
to
9809762
Compare
test:mpich/ch3/tcp |
9809762
to
262f2a9
Compare
test:mpich/ch3/tcp |
262f2a9
to
a658bdb
Compare
test:mpich/warnings/auto |
a658bdb
to
4054b46
Compare
Rebased. One commit ( |
We give user an option to set timeout in MPI_Comm_connect and MPI_Comm_accept. User will need check the error return when time out occurs. Create MPIX_ERR_TIMEOUT for this purpose.
When user set timeout for MPI_Comm_connect and MPI_Comm_accept, we need cancel the pending operations and return proper error code so user can check and handle appropriately.
When MPI_Comm_connect timeout, by convention we return error class MPI_ERR_PORT.
The code to check valid error class was imprecise. Add macros is_valid_err_class and clean it up.
test:mpich/ch3/most |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look OK to me. Is the segfault in ch3 configurations in Jenkins a known issue?
I've seen that failure in unrelated PRs before, but it seems more frequent here, let me re-run the test to confirm. |
test:mpich/ch3/most All clean ✔️ . |
Pull Request Description
When user set timeout for MPI_Comm_connect and MPI_Comm_accept, we need
cancel the pending operations and return the proper error code so user can
check and handle appropriately.
Depends on #5819
Fixes #5815
[skip warnings]
Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short description
Commit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.