Forward-merge branch-25.08 into branch-25.10#1179
Merged
Merged
Conversation
#1089 Scoped Resource access changes were missed in the TieredIndex test causing them to fail. - Using CheckedCuVSResources.create() now - Skip TieredIndex tests if CuVS native support is unavailable Authors: - Puneet Ahuja (https://github.com/punAhuja) Approvers: - Mayya Sharipova (https://github.com/mayya-sharipova) - MithunR (https://github.com/mythrocks) URL: #1156
github-project-automation
Bot
moved this from Todo
to Done
in Unstructured Data Processing
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
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
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.
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.