Skip to content

Forward-merge branch-25.08 into branch-25.10#1154

Merged
GPUtester merged 1 commit into
branch-25.10from
branch-25.08
Jul 23, 2025
Merged

Forward-merge branch-25.08 into branch-25.10#1154
GPUtester merged 1 commit into
branch-25.10from
branch-25.08

Conversation

@rapids-bot

@rapids-bot rapids-bot Bot commented Jul 23, 2025

Copy link
Copy Markdown
Contributor

Forward-merge triggered by push to branch-25.08 that creates a PR to keep branch-25.10 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

…neighbors` (#1072)

In MG all_neighbors, some GPUs stay idle when `n_clusters < n_ranks` (this is the expected behavior). Adding warning to let users know that they are not fully using all GPUs and providing directions for better utilization.

Authors:
  - Jinsol Park (https://github.com/jinsolp)

Approvers:
  - Corey J. Nolet (https://github.com/cjnolet)

URL: #1072
@rapids-bot rapids-bot Bot requested a review from a team as a code owner July 23, 2025 03:26
@GPUtester GPUtester merged commit b822574 into branch-25.10 Jul 23, 2025
2 checks passed
@github-actions github-actions Bot added the cpp label Jul 23, 2025
@rapids-bot

rapids-bot Bot commented Jul 23, 2025

Copy link
Copy Markdown
Contributor Author

SUCCESS - forward-merge complete.

landrumb pushed a commit to landrumb/cuvs that referenced this pull request Jul 8, 2026
Forward-merge branch-25.08 into branch-25.10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants