Fix mypy issue

[wence-]

Description

This was missed while merging #22365

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ef0fc78c-94dd-4eb9-9f8c-39f9dd4eb865

📥 Commits

Reviewing files that changed from the base of the PR and between 96a466e and bb772e2.

📒 Files selected for processing (1)

• python/cudf_polars/cudf_polars/experimental/benchmarks/utils_new_frontends.py

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• Chores
  • Updated internal GPU benchmark runner configuration handling for improved benchmark execution clarity.

Walkthrough

Two benchmark runner functions now explicitly pass engine=None to _finalize_benchmark_run instead of omitting the parameter. Both call sites were reformatted into multiline argument lists for consistency and clarity.

Changes

Benchmark finalization calls

Layer / File(s)	Summary
Benchmark finalization calls with explicit engine parameter python/cudf_polars/cudf_polars/experimental/benchmarks/utils_new_frontends.py	run_polars_cpu and run_polars_in_memory explicitly pass engine=None to _finalize_benchmark_run and use multiline call formatting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• rapidsai/cudf#22504: Both PRs touch utils_new_frontends.py and adjust how the benchmark runner passes/handles engine for CPU and in-memory backends through _finalize_benchmark_run.

Suggested labels

Python, improvement, cudf-polars

Suggested reviewers

• pentschev
• TomAugspurger

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Fix mypy issue' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the specific changeset.	Make the title more specific by describing what mypy issue was fixed, such as 'Fix mypy type checking by explicitly passing engine=None to _finalize_benchmark_run calls'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is related to the changeset as it references a missed change from a prior merge, which aligns with the actual code modifications to fix a mypy issue.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[davidwendt]

/merge