NVIDIA / NVIDIA/cudf

[BUG]: Hang in `test_select_drop_nulls_aggs[ray-aggs1]` in cudf-polars tests

Open
#23,804 0 comments 0 reactions 0 assignees View on GitHub
bug cudf-polars
Dominant language
C++
Stars
9.8k
Forks
1.1k
Avg merge
3d 6m
Merged PRs (30d)
278

Description

**Describe the bug**

https://github.com/NVIDIA/cudf/actions/runs/32816649081/job/97706230710 contains a very large traceback from a test failure.

Using the timing inserted in the logs, the last successful test was at `2026-08-25T06:35:14.7069533Z`. Our timeout fired at `2026-08-25T07:58:12.1429258Z`, 80 minutes later. The python traceback indicates that we're inside `test_select_drop_nulls_aggs[ray-aggs1]`. That looks like a hang, rather than just slow nodes that we've seen previously.

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions job and the `test_select_drop_nulls_aggs[ray-aggs1]` test, using the reported timestamps and Python traceback to reproduce or localize the hang. Done means the test no longer hangs until the timeout and the relevant cudf-polars test run completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.