Skip to content

Forward-merge release/25.12 into main #693

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.

Sign up for GitHub

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

Jump to bottom
Open
rapids-bot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Forward-merge release/25.12 into main #693

rapids-bot wants to merge 2 commits into from

Conversation

@rapids-bot
Copy link
Contributor

@rapids-bot rapids-bot bot commented Dec 11, 2025

Forward-merge triggered by push to release/25.12 that creates a PR to keep main 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.

@aliceb-nv
CI crash fixes (#691)
dddf42d 
## Summary by CodeRabbit

## Release Notes

* **Performance**
  * Optimized branch-and-bound algorithm with improved search termination conditions
  
* **Improvements**
  * Enhanced concurrency control mechanisms across solver components
  * Improved logger initialization and lifecycle management for better resource handling

<sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>

Authors:
  - Alice Boucher (https://github.com/aliceb-nv)

Approvers:
  - Nicolas Blin (https://github.com/Kh4ster)

URL: #691
@rapids-bot rapids-bot bot requested a review from a team as a code owner December 11, 2025 16:52
@rapids-bot rapids-bot bot requested review from akifcorduk and aliceb-nv December 11, 2025 16:52
@rapids-bot
Copy link
Contributor Author

rapids-bot bot commented Dec 11, 2025

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@AyodeAwe AyodeAwe requested a review from a team as a code owner December 11, 2025 19:29
@AyodeAwe AyodeAwe requested a review from jakirkham December 11, 2025 19:29
This was referenced Dec 12, 2025
Closed
Closed
@rgsl888prabhu
Copy link
Collaborator

rgsl888prabhu commented Dec 12, 2025

@AyodeAwe I tried to create forward merge manual PR, but there seems to be some kind of error which pickup tag 25.12 instead of 26.02 #696

@rgsl888prabhu rgsl888prabhu mentioned this pull request Dec 15, 2025
Closed
@github-actions
Copy link

github-actions bot commented Dec 20, 2025

🔔 Hi @anandhkb, this pull request has had no activity for 7 days. Please update or let us know if it can be closed. Thank you!

If this is an "epic" issue, then please add the "epic" label to this issue.
If it is a PR and not ready for review, then please convert this to draft.
If you just want to switch off this notification, then use the "skip inactivity reminder" label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@akifcorduk akifcorduk Awaiting requested review from akifcorduk akifcorduk is a code owner automatically assigned from NVIDIA/cuopt-engine-codeowners

@aliceb-nv aliceb-nv Awaiting requested review from aliceb-nv aliceb-nv is a code owner automatically assigned from NVIDIA/cuopt-engine-codeowners

@jakirkham jakirkham Awaiting requested review from jakirkham jakirkham is a code owner automatically assigned from NVIDIA/cuopt-ci-codeowners

1 more reviewer

@kmk142789 kmk142789 kmk142789 approved these changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@rgsl888prabhu @kmk142789 @aliceb-nv @AyodeAwe