Cleanup the legacy engines code path#22488
Conversation
|
Note Reviews pausedUse the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR eliminates global default executor configuration from the cudf_polars testing infrastructure by making engine specification explicit throughout. It requires all assertion functions to accept explicit ChangesTesting and Benchmark Engine Parameterization
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes The review involves understanding the systematic removal of a global executor pattern across multiple test files and assertion utilities, verifying that all test branches correctly specify engines, and validating the large consolidation of benchmark utilities that introduces comprehensive CLI infrastructure and multi-frontend execution orchestration. Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a Comment |
| @@ -1,19 +1,33 @@ | |||
| # SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. | |||
There was a problem hiding this comment.
This diff is hard to read on GitHub. To better isolate the changes in
utils.py, use something like:
git diff \
main:python/cudf_polars/cudf_polars/experimental/benchmarks/utils_new_frontends.py \
HEAD:python/cudf_polars/cudf_polars/experimental/benchmarks/utils.py
This stuff has already gone, no? |
This is closed by refusing to do it, AFAICT, rather than shoveling an engine argument into |
wence-
left a comment
There was a problem hiding this comment.
Please update the PR description for what is now actually going on.
TBH, I would prefer just changing the benchmark rather than the benchmark and the tests in this PR
| return final_polars_collect_kwargs, final_cudf_collect_kwargs | ||
|
|
||
|
|
||
| def assert_collect_raises( |
There was a problem hiding this comment.
Inlining it instead of calling assert_collect_raises is simpler IMO.
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Fair point, let's do one at a time: #22504 |
|
close in favor of #22535 |
Test helpers (
cudf_polars/testing/asserts.py)assert_collect_raisesTests
test_collect_assert_raisesassert_collect_raisesimports (intest_asserts.py,test_stringfunction.py,test_casting.py,test_datetime_basic.py)Benchmark CLI (
benchmarks/utils.py)--executorflag and folded itscpuandin-memorychoices into--frontend, which now accepts:cpu,in-memory,spmd,ray,dask, andduckdb.ExecutorTypealiasRunConfig.executorassert_never(run_config.executor)branchassert_neverimportBenchmark shim
benchmarks/utils_new_frontends.py(contents merged into
benchmarks/utils.py)