[adriencaccia]

Points the runner at valgrind-codspeed 3.26.0-0codspeed12, which stops simulated arm64 programs from dying with SIGILL when they read a previously unsupported CPU ID register or TPIDRRO_EL0 (CodSpeedHQ/valgrind-codspeed#59). It also ships the opt-in --deterministic-rng flag from 0codspeed11, which the runner does not pass yet.

The 6 hashes match the release's asset digests.

Refs COD-4094, which stays open for the runner v5.6.2 release this unblocks.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This PR appears safe to merge; no actionable issues were found.

Summary

Updates the pinned Valgrind build from 3.26.0-0codspeed10 to 3.26.0-0codspeed12.

• Linux Valgrind setup now uses release iteration 12.

_{Reviews (1) · Last reviewed commit: "chore: bump pinned valgrind-codspeed to ..." · Reviewed by Greptile}

[codspeed]

Merging this PR will degrade performance by 12.87%

2 warnings

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ 8 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 regressed benchmark
✅ 40 untouched benchmarks
⏩ 6 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Walltime	memtrack track tar	8.2 s	9.4 s	-12.87%

Tip

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

---

_{Comparing cod-4094-release-valgrind-codspeed-and-runner (8607d16) with main (ea54386)}

Footnotes

1. 6 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. ↩