Skip to content

Forward-merge release/26.08 into main - #23474

Open
rapids-bot[bot] wants to merge 2 commits into
mainfrom
release/26.08
Open

Forward-merge release/26.08 into main#23474
rapids-bot[bot] wants to merge 2 commits into
mainfrom
release/26.08

Conversation

@rapids-bot

@rapids-bot rapids-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Forward-merge triggered by push to release/26.08 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.

## Description
Upgrades nvcomp to version 5.3.0.16.

Depends on rapidsai/rmm#2462.

Replaces #23294.

## Checklist
- [x] I am familiar with the [Contributing
Guidelines](https://github.com/rapidsai/cudf/blob/HEAD/CONTRIBUTING.md).
- [x] New or existing tests cover these changes.
- [x] The documentation is up to date with these changes.

---------

Co-authored-by: Bradley Dice <bdice@bradleydice.com>
Co-authored-by: Vukasin Milovanovic <vmilovanovic@nvidia.com>
@rapids-bot
rapids-bot Bot requested review from a team as code owners July 29, 2026 17:30
@rapids-bot
rapids-bot Bot requested a review from KyleFromNVIDIA July 29, 2026 17:30
@rapids-bot

rapids-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

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.

@github-actions github-actions Bot added libcudf Affects libcudf (C++/CUDA) code. Python Affects Python cuDF API. CMake CMake build issue Java Affects Java cuDF API. labels Jul 29, 2026
## Description

On `main` and `release/26.08`, the following will error reliably:

```
pytest -p no:randomly -n0 \
	python/cudf_polars/tests/streaming/test_ray.py::test_yields_engine \
	python/cudf_polars/tests/quent/test_quent_integration.py
```

In CI, it will fail if a worker that previously happened to run one of
the ray tests with 0 GPUs happened to worksteal the quent integration
tests.

This fixes the issue by passing through `ray_init_options` and
`ray_num_ranks` when creating the RayEngine for the quent tests, similar
to the rest of the tests

Closes #23441

## Checklist
- [x] I am familiar with the [Contributing
Guidelines](https://github.com/rapidsai/cudf/blob/HEAD/CONTRIBUTING.md).
- [x] New or existing tests cover these changes.
- [x] The documentation is up to date with these changes.
@vyasr
vyasr requested a review from a team as a code owner July 31, 2026 08:42
@vyasr
vyasr requested a review from rjzamora July 31, 2026 08:42
@github-actions github-actions Bot added the cudf-polars Issues specific to cudf-polars label Jul 31, 2026
@GPUtester GPUtester moved this to In Progress in cuDF Python Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CMake CMake build issue cudf-polars Issues specific to cudf-polars Java Affects Java cuDF API. libcudf Affects libcudf (C++/CUDA) code. Python Affects Python cuDF API.

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

4 participants