v5.0.x: update platform file, and fix a UCC fallback issue #13071
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
bosilca
approved these changes
Jan 30, 2025
bosilca
approved these changes
Jan 30, 2025
|
bot:aws:retest |
janjust
force-pushed
the
v5.0.x-prs
branch
2 times, most recently
from
6ce3030 to
89ed5f2
Compare
Signed-off-by: Tomislav Janjusic <[email protected]>
Signed-off-by: Tomislav Janjusic <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
There are 2 commits in this PR independent of each other.
The first one just updates a platform file.
The second commit fixes a coll/ucc component issue.
Users can trigger the issue by changing the priority of collectives so that the UCC component doesn't have a fallback option.
This PR will simply set the fallback to NULL and let upper layer run the fallback collective according to priority order.
Main branch doesn't have this issue because UCC doesn't require backend collective modules.
bot:notacherrypick