TestEngineering/Performance/FAQ: Difference between revisions

Line 271: Line 271:


Those situations appear because a regression appears first on one repo (e.g. autoland) and it takes a few days until the causing commit gets merged to other repos (inbound, beta, central).
Those situations appear because a regression appears first on one repo (e.g. autoland) and it takes a few days until the causing commit gets merged to other repos (inbound, beta, central).
<br />
=== How do I follow up on already open regressions open by me? ===
You can follow up on all the open regression bugs created by you by searching in [https://bugzilla.mozilla.org/query.cgi?format=advanced Advanced search] for bugs with:
<br />
'''Summary:''' contains all of the strings > regression on push
<br />
'''Status:''' NEW, ASSIGNED, REOPENED<br />
<br />
[[File:Advanced search for perf regressions.png|1200px|Advanced search for perf regressions]]
<br />
'''Keywords:''' perf, perf-alert, regression
<br />
'''Type:''' defect
<br />
[[File:Advanced search for perf regressions type.png|700px|Advanced search for perf regressions type]]
<br />
'''Search by People:''' ''The reporter is'' > [your email]<br />
[[File:Advanced search for perf regressions by people.png|200px|Advanced search for perf regressions by people]]
<br />
<br />
And you will get the list of all open regressions reported by you:
<br />
[[File:Advanced search results.png|1200px|Advanced search results]]
342

edits