-
Notifications
You must be signed in to change notification settings - Fork 934
oob ud: fixes and parameter adjustment #536
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
orte/mca/oob/ud/oob_ud_component.c
Outdated
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.
If this is intended to convey an error message to the end user (vs. an OMPI developer), opal_show_help() should be used instead.
Ditto for all the opal_output()'s in this PR.
|
|
Refer to this link for build results (access rights to CI server needed): |
|
@jsquyres Since review of whole component is needed in order to replace all similar outputs I propose to use another one PR. Otherwise it would be difficult to see the difference between formal changes and real fixes in the same PR. |
|
@nkogteva That would be fine, but then you should strip all the opal_output_verbose -> opal_output conversions from this PR. Specifically: it does not make sense to me to commit something that makes a situation worse with the rationale that it will be fixed in the future (because that inevitably does not happen). Even more specifically: it seems like this PR is two different things, anyway: some fixes and some opal_output_verbose->opal_output conversions. So strip those out and make a 2nd PR to comprehensively convert all opal_output*'s of errors into opal_show_helps. |
|
|
@nkogteva Thank you! |
|
Refer to this link for build results (access rights to CI server needed): |
|
👍 |
oob ud: fixes and parameter adjustment
…on_bugfix Java garbage collection bugfix
Adding an Preexec option to mpirun
No description provided.