Skip to content

ci: bisect walltime shard 2 hang (do not merge) - #144

Closed
GuillaumeLagrange wants to merge 9 commits into
masterfrom
debug/walltime-bisect
Closed

GuillaumeLagrange wants to merge 9 commits into
masterfrom
debug/walltime-bisect

Conversation

@GuillaumeLagrange

Copy link
Copy Markdown
Contributor

Throwaway bisect of the shard 2 hang seen on #141. Refs COD-4043

claude and others added 7 commits October 28, 2026 10:33
pytest 9.2 replaced the private `FixtureManager._arg2fixturedefs` with
`_arg2node2fixturedefs` (pytest-dev/pytest#14984). The
`pytest_plugin_registered` hook wrote into `_arg2fixturedefs` to swap
pytest-benchmark's `benchmark` fixture for ours, so every `--codspeed`
run with pytest-benchmark installed crashed with an AttributeError.

On pytest 9.1+, register the override through the public
`pytest.register_fixture` API at session start instead. Older pytest
keeps the previous `_arg2fixturedefs` swap.

pytest-benchmark itself still reads the removed `Node._nodeid` on
pytest 9.2, so the two tests that run it without `--codspeed` are
marked as non-strict xfail on that combination.

Co-Authored-By: Guillaume Lagrange <19265358+GuillaumeLagrange@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…chmark

The matrix only installed the latest pytest, so the fixture override
paths for pytest without register_fixture (9.0) and before 8.1.1 were
never exercised. Add pytest 9.0 and 8.0 jobs on Python 3.15 only, to
avoid the full combinatorial matrix.

The valgrind install condition matched a "pytest-benchmark" config that
no longer exists since the split into -4 and -5, so the valgrind tests
running --codspeed with pytest-benchmark installed were always skipped.

Co-Authored-By: Claude <noreply@anthropic.com>
@codspeed

codspeed Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Merging this PR will regress 1 benchmark

1 warning

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

⚡ 3 improved benchmarks
❌ 1 regressed benchmark
✅ 24 untouched benchmarks
⏩ 302 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Benchmark BASE HEAD Efficiency
❌ test_generate_all_combinations[5-4] 10.2 µs 10.8 µs -5.17%
⚡ test_multiprocessing_map[10000] 98.6 ms 55.2 ms +78.77%
⚡ test_pipe_communication[10000] 12.1 ms 11.3 ms +7.06%
⚡ test_make_lowpass 5.6 µs 5.2 µs +6.47%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing debug/walltime-bisect (c4c257d) with master (5af4238)

Open in CodSpeed

Footnotes

  1. 302 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@GuillaumeLagrange

Copy link
Copy Markdown
Contributor Author

Closing throwaway debug PR (COD-4043).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants