mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-25 11:58:55 +00:00

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
…
…
…
Bug 1682947 - Use MADV_FREE_REUSE before using decommitted memory again on OSX, as per https://bugs.chromium.org/p/chromium/issues/detail?id=823915 r=glandium
…
…
…
…
…
…
…
…
…
…
An explanation of the Firefox Source Code Directory Structure and links to project pages with documentation can be found at: https://firefox-source-docs.mozilla.org/contributing/directory_structure.html For information on how to build Firefox from the source code and create the patch see: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html If you have a question about developing Firefox, and can't find the solution on https://firefox-source-docs.mozilla.org/, you can try asking your question on Matrix at chat.mozilla.org in `Introduction` (https://chat.mozilla.org/#/room/#introduction:mozilla.org) channel. Nightly development builds can be downloaded from: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ - or - https://www.mozilla.org/firefox/channel/desktop/#nightly Keep in mind that nightly builds, which are used by Firefox developers for testing, may be buggy.
Description
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
Languages
JavaScript
32.3%
C++
25.4%
HTML
21%
C
10.8%
Python
2.8%
Other
7.2%