Skip to content

Conversation

@GuillaumeLagrange
Copy link
Contributor

No description provided.

Users should prefer `go build` -> codspeed exec -- ./my_binary` workflow
but this allows basic support for `go run .`

These flags are necessary to
1. Keep the binary after `go run` completes, for symbol and debug info parsing
2. Not strip symbols and debug infos from the binary

`GOFLAGS` do not work with either of these forms
`GOFLAGS="-work -ldflags=-s=false -ldflags=-w=false"`
`GOFLAGS="-work -ldflags='-s=false -w=false'"`
`GOFLAGS='-work -ldflags="-s=false -w=false"'`

Ended up giving up and relying on the introspected go
@codspeed-hq
Copy link

codspeed-hq bot commented Feb 9, 2026

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing cod-2037-go-in-profiling-cli (f4875b1) with main (829bcf1)

Summary

✅ 4 untouched benchmarks

Copy link
Member

@not-matthias not-matthias left a comment

Choose a reason for hiding this comment

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

LGTM!

@GuillaumeLagrange GuillaumeLagrange merged commit f4875b1 into main Feb 9, 2026
13 checks passed
@GuillaumeLagrange GuillaumeLagrange deleted the cod-2037-go-in-profiling-cli branch February 9, 2026 12:04
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