342
edits
TestEngineering/Performance/FAQ: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/FAQ (view source)
Revision as of 08:51, 29 January 2020
, 29 January 2020no edit summary
Alexandrui (talk | contribs) (→Noise) |
Alexandrui (talk | contribs) No edit summary |
||
| Line 248: | Line 248: | ||
This doesn't affect Talos alerts as much, but keep in mind that if you cannot determine a trend for an alerted regression and have done a lot of retriggers, then it is probably not worth the effort to find the root cause. | This doesn't affect Talos alerts as much, but keep in mind that if you cannot determine a trend for an alerted regression and have done a lot of retriggers, then it is probably not worth the effort to find the root cause. | ||
== Bugzilla == | |||
== How do I identify the current firefox release meta-bug? == | |||
To easily track all the regressions opened, for every Firefox release is created a meta-bug that will depend on the regressions open. | |||
[[File:Advanced search.png|Advanced search]]<br /> | |||
To find all the Firefox release meta-bugs you just have to search in Advanced search for bugs with: | |||
[[File:Firefox 70 meta.png|Firefox 70 meta]]<br /><br /> | |||
'''Product:''' Testing<br /> | |||
'''Component:''' Performance<br /> | |||
'''Summary:''' Contains all of the strings [meta] Firefox, Perfherder Regression Tracking Bug | |||
You can leave the rest of the fields as they are. | |||
[[File:Advanced search filter.png|1200px|Advanced search filter]]<br /> | |||
<br /> | |||
Result:<br /> | |||
[[File:Firefox metabugs.png|1200px|Firefox metabugs]] | |||