TestEngineering/Performance/Triage Process: Difference between revisions

TestEngineering/Performance/Triage Process (view source)

1 byte removed , 18 March 2020

no edit summary

Confirmed users

2,177

edits

Revision as of 14:32, 26 February 2020 (view source) Mjzffr (talk \| contribs) (Explain P1 and ASSIGNED status) ← Older edit		Revision as of 11:14, 18 March 2020 (view source) Davehunt (talk \| contribs) No edit summary Newer edit →
Line 29:		Line 29:

	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 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.


	=== Can I have many bugs assigned to me? ===		=== Can I have many bugs assigned to me? ===