mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-21 17:59:34 +00:00
813445ccd8
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. To use the Sentry ID to identify information about a specific bug report, the bug assignee should open the Mozilla Sentry page for the `mach` project and paste the ID into the search box, which will produce the full stack trace with all submitted information. Differential Revision: https://phabricator.services.mozilla.com/D100247
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025