-
Notifications
You must be signed in to change notification settings - Fork 927
op: Add a default value for MPI_OP o_name #1833
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
Conversation
Build Failed with XL compiler! Please review the log, and get in touch if you have questions. |
Build Failed with GNU compiler! Please review the log, and get in touch if you have questions. |
👍 |
(IBM Jenkins) Something strange is happening with the IBM cluster this morning - I'm trying to diagnose. |
bot:retest |
Build Failed with XL compiler! Please review the log, and get in touch if you have questions. Gist: https://gist.github.com/5bc41e28bae363aaacfe61645dd6425f |
:bot:retest |
Test FAILed. |
Humm. The LANL Jenkins is showing something the the IBM Jenkins was showing on some other PRs: [ompi:32674] listen_thread: accept() failed: Invalid argument (22). I wonder if this is a regression in the master branch that only gets triggered on occasion. It is not related to this PR. bot:retest |
c7adddd
to
0671e45
Compare
Build Failed with XL compiler! Please review the log, and get in touch if you have questions. Gist: https://gist.github.com/812577ac894303c1148f2b700a7e715a |
@jjhursey Yeah. Seeing that periodically on all Jenkins. Maybe something in pmix? |
The IBM failure is due to an unexpected system outage. Once it's back i'll get it to retest. |
bot:mellanox:retest |
For user defined
MPI_Op
types theo_name
field is never set. Some components use this field for verbose output, and leaving it undefined makes the output difficult to review. So this commit makes sure that it gets initialized in all paths.