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
Originally reported by @danp in #69552: an observed crash was not recorded in telemetry.
Investigating why, I discovered that in https://go.dev/cl/592017, the codepath to the telemetry child started bypassing the call to counter.Open, and so while the crashmonitor does in fact report a crash, this report goes nowhere.
Of course, this indicates a critical gap in testing coverage of telemetry.Start.
It looks like gopls@v0.16.2 has this bug as well, but gopls@v0.16.1 does not (I had a note to self to investigate why we'd not received any crash reports for gopls@v0.16.2). The go command is unaffected as it wasn't using crash reporting.
Fix incoming.
The text was updated successfully, but these errors were encountered:
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Sep 27, 2024
Update the x/telemetry dependency to pick up the fix for crash reporting
from golang/go#69681.
For golang/go#69681
Change-Id: Ic8bda6e1e80a5004989567a5e7645ef99cf9130f
Reviewed-on: https://go-review.googlesource.com/c/tools/+/616415
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Robert Findley <rfindley@google.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
Pinkle-pash
added a commit
to Pinkle-pash/telemetry
that referenced
this issue
Dec 4, 2024
Following CL 592017, the child process started by telemetry.Start no
longer opens the counter file, causing crash reports to be dropped on
the floor. Fix this, with a test.
Fixesgolang/go#69681
Change-Id: I423533d5b1e2369f13880cecd9137cd7c9239240
Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/616396
Reviewed-by: Alan Donovan <adonovan@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Robert Findley <rfindley@google.com>
Originally reported by @danp in #69552: an observed crash was not recorded in telemetry.
Investigating why, I discovered that in https://go.dev/cl/592017, the codepath to the telemetry child started bypassing the call to counter.Open, and so while the crashmonitor does in fact report a crash, this report goes nowhere.
Of course, this indicates a critical gap in testing coverage of telemetry.Start.
It looks like gopls@v0.16.2 has this bug as well, but gopls@v0.16.1 does not (I had a note to self to investigate why we'd not received any crash reports for gopls@v0.16.2). The go command is unaffected as it wasn't using crash reporting.
Fix incoming.
The text was updated successfully, but these errors were encountered: