-
Notifications
You must be signed in to change notification settings - Fork 8
feat: add MacOS support #81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
not-matthias
wants to merge
3
commits into
main
Choose a base branch
from
cod-2720-bump-instrument-hooks-in-codspeed-node-to-support-macos
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule hooks
updated
8 files
| +16 −0 | .github/workflows/ci.yml | |
| +11,566 −11,193 | dist/core.c | |
| +37 −25 | includes/callgrind.h | |
| +5 −0 | includes/core.h | |
| +5 −0 | scripts/stub.c | |
| +24 −0 | src/c.zig | |
| +1 −0 | src/helpers/valgrind.zig | |
| +6 −0 | src/helpers/valgrind_wrapper.c |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| /** | ||
| * Wrap a benchmark function so it executes under a frame named | ||
| * `__codspeed_root_frame__`. CodSpeed uses this frame to locate the | ||
| * benchmark root in collected call stacks; samples without it cannot be | ||
| * attributed to a benchmark. | ||
| */ | ||
| export function wrapWithRootFrame<T>( | ||
| fn: () => T | Promise<T>, | ||
| ): () => Promise<T> { | ||
| return async function __codspeed_root_frame__() { | ||
| return await fn(); | ||
| }; | ||
| } | ||
|
|
||
| export function wrapWithRootFrameSync<T>(fn: () => T): () => T { | ||
| return function __codspeed_root_frame__() { | ||
| return fn(); | ||
| }; | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| import { bench, describe } from "vitest"; | ||
|
|
||
| const isMacOS = process.platform === "darwin"; | ||
|
|
||
| function fibo(n: number): number { | ||
| if (n < 2) return 1; | ||
| return fibo(n - 1) + fibo(n - 2); | ||
| } | ||
|
|
||
| // macOS-only benchmark: skipped on every other platform, so it only runs on | ||
| // the `codspeed-walltime-macos` CI job (see .github/workflows/codspeed.yml). | ||
| describe.skipIf(!isMacOS)("macos only", () => { | ||
| bench("fibo darwin", () => { | ||
| fibo(30); | ||
| }); | ||
| }); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stopBenchmark(), violating the required nestingThe code comment on
sendBenchmarkMarkersexplicitly states markers must land inside the sample window — i.e. beforestopBenchmark()closes it. Thefinallyblock here does the opposite:stopBenchmark()is called first, thensendBenchmarkMarkersis called, placing both markers outside the sample window. The same ordering mistake exists inwrapWithInstrumentHooksAsync.The integration test added in this PR (
emits benchmark markers inside the sample window in walltime mode) assertsmarkerOrder < stopOrderand will fail with the current order. The correct order mirrors whatvitest-plugin/src/walltime/index.tsalready does: emit both markers, then callstopBenchmark().