Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Jump to navigation
Jump to search
Sheriffing/How To/Intermittent bugs (view source)
Revision as of 07:49, 19 October 2021
, 19 October 2021→How to file a security bug: mention Treeherder's support for filing security bugs and that manual process is a fallback
(→Machine-specific failures: update example how to terminate machine) |
(→How to file a security bug: mention Treeherder's support for filing security bugs and that manual process is a fallback) |
||
| Line 166: | Line 166: | ||
== How to file a security bug == | == How to file a security bug == | ||
'''NOTE''': Treeherder supports the creation of security bugs from its bug filer. The process described below should be used if that feature stopped working or a bug has to be filed outside Treeherder | |||
When we see failures which contains “use-after-poison” in the log, it usually means that we have to file a security bug for it. Security bugs are '''not''' visible except when you are on the CC list. | When we see failures which contains “use-after-poison” in the log, it usually means that we have to file a security bug for it. Security bugs are '''not''' visible except when you are on the CC list. | ||
| Line 183: | Line 185: | ||
* stack-buffer-underflow | * stack-buffer-underflow | ||
* use-after-poison | * use-after-poison | ||
How to file such a bug: | How to file such a bug: | ||
# Access '''Bugzilla''' (https://bugzilla.mozilla.org/enter_bug.cgi) and search after the relevant Component, in this case Core :: Layout. | # Access '''Bugzilla''' (https://bugzilla.mozilla.org/enter_bug.cgi) and search after the relevant Component, in this case Core :: Layout. | ||