Confirmed users
378
edits
TestEngineering/Performance/Triage Process: Difference between revisions
Jump to navigation
Jump to search
m
TestEngineering/Performance/Triage Process (view source)
Revision as of 14:58, 29 April 2020
, 29 April 2020→How to handle intermittent bugs which cover a crash of Firefox?: -
m (add links, reorg) |
|||
| Line 80: | Line 80: | ||
** Don’t rush & assume that the 1st frame of the crashing thread is the culprit, especially if its corresponding source code points to a header (*.h) file | ** Don’t rush & assume that the 1st frame of the crashing thread is the culprit, especially if its corresponding source code points to a header (*.h) file | ||
** If indeed 1st frame isn’t the culprit, just go to the next frame from the logs. | ** If indeed 1st frame isn’t the culprit, just go to the next frame from the logs. | ||
** Note: most often, this is not a trivial task. So even if you end up to another source file, it’s still very likely that the problem happens a bit more up the stack. If you get blocked, request an engineer’s assistance | ** Note: most often, this is not a trivial task. So even if you end up to another source file, it’s still very likely that the problem happens a bit more up the stack. If you get blocked, request an engineer’s assistance and learn from their process. | ||
* How do you know which engineer to ask for assistance? | * How do you know which engineer to ask for assistance? | ||
** By looking over the source file (you got stuck at) & figuring out its component (use Mercurial’s blame feature). With that component, you identify the team that likely has more knowledge over the problem. Contact | ** By looking over the source file (you got stuck at) & figuring out its component (use Mercurial’s blame feature). With that component, you identify the team that likely has more knowledge over the problem. Contact the team & ask someone there to assist you. | ||
** You can also search for the associated file name in [https://searchfox.org/ searchfox], and find the corresponding Bugzilla component within the nearest <code>moz.build</code> file. | ** You can also search for the associated file name in [https://searchfox.org/ searchfox], and find the corresponding Bugzilla component within the nearest <code>moz.build</code> file. | ||
== FAQ == | == FAQ == | ||