Skip to content

fix(runner): check benchmark URIs rather than memtrack events#230

Open
not-matthias wants to merge 1 commit intomainfrom
cod-2170-memory-profiling-fails-when-there-are-0-events
Open

fix(runner): check benchmark URIs rather than memtrack events#230
not-matthias wants to merge 1 commit intomainfrom
cod-2170-memory-profiling-fails-when-there-are-0-events

Conversation

@not-matthias
Copy link
Member

Memory profiling can be empty, if the benchmark has no allocations. We shouldn't fail in those cases.

Memory profiling can be empty, if the benchmark has no allocations. We shouldn't fail in those cases.
@not-matthias not-matthias force-pushed the cod-2170-memory-profiling-fails-when-there-are-0-events branch from 481c245 to ce286fe Compare February 2, 2026 16:57
@codspeed-hq
Copy link

codspeed-hq bot commented Feb 2, 2026

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing cod-2170-memory-profiling-fails-when-there-are-0-events (ce286fe) with main (920c7a1)

Summary

✅ 4 untouched benchmarks

Copy link
Contributor

@GuillaumeLagrange GuillaumeLagrange left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, dont forget to test both success and failure to make sure we did not invert a boolean this time 🙃

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