[GuillaumeLagrange]

Related: CodSpeedHQ/samply-codspeed#14

Closes COD-4043

[greptile-apps]

Confidence Score: 5/5

[Medium impact] No confirmed issue blocks merging.

Summary

Updates crates/samply-codspeed to 2eaaf6e72aba2cb1c0c5f6257969908b617a7bc4, intended to prevent looping on corrupted JIT dumps.

• Wall-time profiling no longer loops on corrupted JIT dumps.

_{Reviews (2) · Last reviewed commit: "samply-codspeed: bump submodule to not l..." · Reviewed by Greptile}

[codspeed]

Merging this PR will not alter performance

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

✅ 41 untouched benchmarks
⏩ 6 skipped benchmarks¹

---

_{Comparing cod-4043-jitdump-malformed-record (6c5b646) with main (d14d95d)}

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

[not-matthias]

lgtm, don't forget to update the submodule ref to exclude the stack cache changes