-
Notifications
You must be signed in to change notification settings - Fork 859
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
5.0.x/opal/cuda: Handle stream-ordered allocations and assign primary device #12843
5.0.x/opal/cuda: Handle stream-ordered allocations and assign primary device #12843
Conversation
Hello! The Git Commit Checker CI bot found a few problems with this PR: fdb497d: opal/cuda: Handle stream-ordered allocations and a...
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
fdb497d
to
c09e947
Compare
Hello! The Git Commit Checker CI bot found a few problems with this PR: c09e947: opal/cuda: Handle stream-ordered allocations and a...
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 4537ce9: Merge branch 'v5.0.x' into topic/5.0.x/handle-masy...
c09e947: opal/cuda: Handle stream-ordered allocations and a...
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
4537ce9
to
6984154
Compare
Hello! The Git Commit Checker CI bot found a few problems with this PR: 6984154: opal/cuda: Handle stream-ordered allocations and a...
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
correct |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 6984154: opal/cuda: Handle stream-ordered allocations and a...
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
@Akshay-Venkatesh please do another cherry-pick amend, I think after you opened this PR, and then forced push to the main PR, the hash is different now, thus the commit checker will fail. |
6984154
to
fd9cd3f
Compare
@janjust Does this look like a related error https://github.com/open-mpi/ompi/actions/runs/11219955917/job/31192809106?pr=12843#step:9:26 ? |
…e context Signed-off-by: Akshay Venkatesh <[email protected]> (cherry picked from commit cafcce9)
fd9cd3f
to
54f4ba4
Compare
Rebased to pick up mpi4py github action fix. |
Port of #12835