Compiling the tempo CLI fails with go 1.23 on openSUSE?

[johanneskastl]

Describe the bug
I am packaging the tempo CLI for openSUSE. The package fails to build on all build targets that are using go1.23. Older targets that only have go1.22 are building fine.

[   35s] + go build -mod=vendor -buildmode=pie '-ldflags=    -X main.Branch=v2.6.0    -X main.Revision=e85bbc57    -X main.Version=2.6.0' -o bin/tempo-cli ./cmd/tempo-cli
[   51s] # github.com/grafana/pyroscope-go/godeltaprof/internal/pprof
[   51s] vendor/github.com/grafana/pyroscope-go/godeltaprof/internal/pprof/delta_mutex.go:30:20: undefined: runtime_cyclesPerSecond
[   51s] vendor/github.com/grafana/pyroscope-go/godeltaprof/internal/pprof/proto.go:320:8: undefined: runtime_expandFinalInlineFrame
[   85s] error: Bad exit status from /var/tmp/rpm-tmp.i0uDKH (%build)

This happens with v2.5.0 and v2.6.0.

Manually overriding the go version on e.g. Tumbleweed to go1.22 fixes the issue and the build succeeds.

Kind Regards,
Johannes

[mapno]

Hi, thanks for reporting. Apparently, it's been fixed in godeltaprof (grafana/pyroscope-go#119) and updated in Tempo (#4006). But the change didn't make it to v2.6. We'd need to patch those releases for this to work without the override.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.

[johanneskastl]

Hi, thanks for reporting. Apparently, it's been fixed in godeltaprof (grafana/pyroscope-go#119) and updated in Tempo (#4006). But the change didn't make it to v2.6. We'd need to patch those releases for this to work without the override.

Any news on this?

[mapno]

Hi. We're targeting to have v2.7 around end of year/early January

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.

[darix]

2.7.0 is out and our package is building with 1.23, but i cant close the issue.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.