Skip to content

fix(runner): check child status code after valgrind#72

Merged
not-matthias merged 1 commit intomainfrom
cod-665-crash-in-valgrind-doesnt-display-valgrind-logs
Mar 14, 2025
Merged

fix(runner): check child status code after valgrind#72
not-matthias merged 1 commit intomainfrom
cod-665-crash-in-valgrind-doesnt-display-valgrind-logs

Conversation

@not-matthias
Copy link
Member

Prints the valgrind logs now:

[DEBUG::codspeed::run::runner::valgrind::measure] Valgrind exit code = None, Valgrind signal = Some(11)
[DEBUG::codspeed::run::runner::valgrind::measure] valgrind.log: ==303374== Using source line as position.
--303374-- warning: L3 cache found, using its data for the LL simulation.
--303374-- warning: specified LL cache: line_size 64  assoc 12  total_size 18,874,368
--303374-- warning: simulated LL cache: line_size 64  assoc 18  total_size 18,874,368

Error: failed to execute valgrind

Before it only printed this:

Error: cannot parse integer from empty string

@not-matthias not-matthias force-pushed the cod-665-crash-in-valgrind-doesnt-display-valgrind-logs branch from 139c3e7 to 7b3a19c Compare March 14, 2025 13:21
@not-matthias not-matthias requested review from art049 and removed request for GuillaumeLagrange March 14, 2025 13:26
Copy link
Member

@art049 art049 left a comment

Choose a reason for hiding this comment

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

Claud LGTM

@not-matthias not-matthias merged commit 7b3a19c into main Mar 14, 2025
9 checks passed
@not-matthias not-matthias deleted the cod-665-crash-in-valgrind-doesnt-display-valgrind-logs branch March 14, 2025 14:30
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