usNIC: fix fi_ep_bind flag. FI_RECV should not be associated with address vector. #3539
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Thananon Patinyasakdikul <[email protected]>
jsquyres
approved these changes
May 16, 2017
|
Seems to be a false failure in the PRBC CI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FI_RECV is not a valid flag for address vector. This is a bug where usNIC libfabric provider does not validate the flag. There will be fix coming up from libfabric side for OMPI reverse compatibility.
Signed-off-by: Thananon Patinyasakdikul [email protected]