Closed Bug 1678668 Opened 3 years ago Closed 3 years ago

An identifier for the Sentry report should be attached to the "exception occurred" print dump

Categories

(Firefox Build System :: Mach Core, enhancement)

enhancement

Tracking

(firefox86 fixed)

RESOLVED FIXED
86 Branch
Tracking Status
firefox86 --- fixed

People

(Reporter: mhentges, Assigned: sheehan)

Details

Attachments

(1 file)

When issues are reported on bugzilla, it's always helpful when the reporter includes the Mach log including the failure.

Since exceptions caught by Mach are submitted to Sentry, it would be helpful to link between the Sentry report (with stack trace information, versioning information, tags, etc) and the bugzilla report.

As suggested by Connor, if we include a Sentry event identifier in the mach exception print dump.

Assignee: nobody → sheehan

When mach errors out, an error report is sent to Sentry. This error
report contains information about the state of the interpreter during
the failure, details about the environment, installed packages and more.
Having this information available immediately when attempting to resolve
a bug report is generally desirable, instead of going through a back-and-forth
needinfo tag on Bugzilla or spending time asking the reporter questions on
Matrix.

This commit captures the Sentry ID returned from sentry_sdk.capture_exception
and prints it to the screen. If a user adds this line to their bug report (as
the error messages suggest) a build team member can enter this number into
Sentry to identify the exact report and debug the error. At minimum this will
reduce the amount of back-and-forth between the reporter and the assignee
required to resolve a bug. Optimally it should make bugs easier to spot and
reduce the time spent on end user support requests.

Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2804a2a2c4a7
print sentry error report number on mach command failure r=firefox-build-system-reviewers,mhentges
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: