GeezerVison

The test dependency group now includes pytest-xdist. The CodSpeed benchmark command uses -n auto to run tests with automatically selected workers.

Changes: CodSpeed benchmark parallelism

Layer / File(s)	Summary
Enable parallel benchmark execution pyproject.toml, .github/workflows/codspeed.yml	The test dependency group adds pytest-xdist. The CodSpeed command runs pytest tests/ --codspeed -n auto.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · up to 8196c

The benchmark job runs in parallel. No merge-blocking issue is established; normal CI verification remains appropriate.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title "ci: run CodSpeed benchmarks in parallel with pytest-xdist" matches the main change. The CodSpeed workflow now runs pytest with the -n auto option. The test extra in pyproject.toml now inclu…
Linked Issues check		[#663] The issue requires running the CodSpeed benchmark job in parallel under simulation mode, without dropping benchmarks. It proposes pytest tests/ --codspeed -n auto and adding pytest-xdist to…
Out of Scope Changes check		The whole-PR summary lists two reviewed changes. Both implement #663. .github/workflows/codspeed.yml changes only the benchmark run command to add -n auto. pyproject.toml changes only the test…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…

Full details: Title check

Explanation

The title "ci: run CodSpeed benchmarks in parallel with pytest-xdist" matches the main change. The CodSpeed workflow now runs pytest with the -n auto option. The test extra in pyproject.toml now includes pytest-xdist, which provides that option. The title is specific, short, and describes the primary intent from the linked issue (reducing the benchmark job runtime by parallelizing). The title does not cover the uv.lock regeneration, but that is a expected omission and the lock file is generated output.

Full details: Linked Issues check

Explanation

[#663] The issue requires running the CodSpeed benchmark job in parallel under simulation mode, without dropping benchmarks. It proposes pytest tests/ --codspeed -n auto and adding pytest-xdist to the test dependencies. The whole-PR summary shows both changes. .github/workflows/codspeed.yml changes the run command to pytest tests/ --codspeed -n auto (+1/-1). pyproject.toml adds pytest-xdist to the test optional dependency group (+1/-1). The benchmark job installs .[test], so the plugin is available to the job. No benchmark is removed or excluded. Sharding across a job matrix is a possible follow-up, not a requirement of #663. The issue does not require new tests. The parallel-safety claim is supported only by the author's local run and the issue text. The PR's own CodSpeed run provides the measurement, as the issue expects. uv.lock is excluded from review (ignored by the !**/*.lock rule). The lock file is a derived artifact of the pyproject.toml change, so the result does not depend on its contents.

Full details: Out of Scope Changes check

Explanation

The whole-PR summary lists two reviewed changes. Both implement #663. .github/workflows/codspeed.yml changes only the benchmark run command to add -n auto. pyproject.toml changes only the test extra to add pytest-xdist. Neither change touches benchmark content, the README, or unrelated CI jobs. The README pin is explicitly unchanged. uv.lock is excluded from review. Its changes are the lock-file result of adding pytest-xdist and execnet, which is a direct consequence of the in-scope pyproject.toml change. No out-of-scope change is identified.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Generate unit tests (beta)

• Create a new PR

• X
• Mastodon
• Reddit
• LinkedIn

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

⚠️ 136 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ 1 benchmark with a significant change ran on different hardware

Its base and head results were measured on machines with a different CPU, core count or memory, so the change might not come from the code. Run base and head on the same runner type.

Learn more about Macro Runners

See affected benchmarks

⚠️ 1 benchmark with a significant change ran in a different software environment

Its base and head results were measured with a different OS or toolchain, such as compiler, runtime or library versions, so the change might come from this difference rather than from the code. Open the benchmark to see what changed.

See affected benchmarks