TestEngineering/Performance/Triage Process: Difference between revisions

TestEngineering/Performance/Triage Process (view source)

391 bytes added , 19 March 2020

canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,714

edits

@@ Line 28: / Line 28: @@
 === How to handle intermittent bugs which cover a crash of Firefox? ===
-First make sure it doesn't stay in the Testing component but gets moved to a product that covers Firefox. Therefore check the crashing thread and find the first stack which is part of our code. Search for the associated file name in searchfox, and find the corresponding Bugzilla component within the nearest moz.build file. If not done yet, also add a comment with the link to the exact crash location. Make sure to keep the changeset id in the URL.
+First make sure it doesn't stay in the Testing component but gets moved to a product that covers Firefox. Therefore check the crashing thread and find the reported crash frame as listed in the summary of the bug. From there go on and find the first frame that is part of our code. Also check for the following:
+* For a header file (.h) you can most likely continue to the next frame
+* If it is inter-process communication (IPC) related remember that various components make use of it, so check higher in the stack, which code calls into the IPC code.
+When you found the final frame, search for the associated file name in searchfox, and find the corresponding Bugzilla component within the nearest moz.build file. If not done yet, also add a comment with the link to the exact crash location. Make sure to keep the changeset id in the URL.
 === Can I have many bugs assigned to me? ===