-
Notifications
You must be signed in to change notification settings - Fork 22
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
Return codes #350
Return codes #350
Conversation
Maybe take a look at these files (based on the order listed in the "files" section of review) @kathrynmohror - 1-4 files |
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.
Finished review of files 10-13
Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.
Here are the meanings for the emojis:
|
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.
I was verifying that the revision exceptions were applied. They all are except the one noted here. Please make that change and then it will be ready for second vote in the next quarterly meeting.
PMIx ASC 3Q 2021
|
@dsolt See the comment above about a Revision Exception change that needs to be resolved before we can merge. PMIx ASC 4Q 2021
|
The signed-off checker stumbled on the "Co-authored-by" - so it is fine to merge. |
7a0ab70
to
97dc620
Compare
Signed-of-by: dsolt@us.ibm.com
Signed-of-by: dsolt@us.ibm.com
Signed-of-by: dsolt@us.ibm.com
Signed-of-by: dsolt@us.ibm.com
Signed-of-by: dsolt@us.ibm.com
Signed-of-by: dsolt@us.ibm.com Mostly cases of using constdesc instead of itemize in lists. Cases of not using the macros when I should have. Cases of adding non-blocking PMIX_OPERATION_SUCCEEDED where I thought it was missing, but in reality those API's can't return that value A few other misc fixes.
Signed-of-by: dsolt@us.ibm.com
Possible revision exceptions: * Get rid of redundant text around cbfunc not being called on error * 2 cases where returnsimple was used where returnsimplenb was intended * Get rid of PMIX_ERR_BAD_PARAM when it adds no useful information to the API * Remove claim that PMIX_OPERATION_SUCCEEDED can only be called when cbfunc is non-null for API's where it is permitted to called for a null cbfunc. * Clarify in returnsimplenb macro that the cbfunc is only called when PMIX_SUCCESS is returned. * Remove implementation assumption from nonblocking macro that assumes processing is done by the "host environment" Signed-of-by: dsolt@us.ibm.com
…ndler Co-authored-by: Josh Hursey <4259120+jjhursey@users.noreply.github.com> Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
97dc620
to
d46aa8a
Compare
I just rebased the branch so it will merge cleanly. Ready to merge once CI is done. |
A review of how return values are presented for each API to be more consistent.