ci: use ctest - #8439
Closed
joseph-isaacs wants to merge 1 commit into
Closed
CodSpeed HQ / CodSpeed Performance Analysis
succeeded
Jun 16, 2026
Performance Gate Passed
⚠️ Unknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.
For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
⚡ 4 improved benchmarks
✅ 1541 untouched benchmarks
⏩ 10 skipped benchmarks1
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
273.6 ns | 215.3 ns | +27.1% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[1024] |
333.9 ns | 275.6 ns | +21.17% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[2048] |
456.9 ns | 398.6 ns | +14.63% |
| ⚡ | Simulation | encode_varbin[(1000, 2)] |
175.3 µs | 157.1 µs | +11.6% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/clean-rust-intru (741703b) with develop (e935986)
Footnotes
-
10 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. ↩
Loading