You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 727b808
Browse filesBrowse the repository at this point in the historyBrowse files
fix(core): exclude the running node executable from callgrind
The runner only passes `--obj-skip` for the `node` it resolves on PATH.
When benchmarks run another binary, such as one provided by a Bazel
toolchain, callgrind records the whole V8 runtime between the JS frames:
thousands of native functions that drown the flamegraph and make it
expensive to process.
Register `process.execPath` on callgrind's obj-skip list in `setupCore`,
through the instrument-hooks client request, as pytest-codspeed does for
the Python executable. It runs before any benchmark starts the
instrumentation, and is a no-op outside Valgrind.
0 commit comments