342
edits
TestEngineering/Performance/FAQ: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/FAQ (view source)
Revision as of 09:27, 29 January 2020
, 29 January 2020→Bugzilla
Alexandrui (talk | contribs) No edit summary |
Alexandrui (talk | contribs) |
||
| Line 266: | Line 266: | ||
Result:<br /> | Result:<br /> | ||
[[File:Firefox metabugs.png|1200px|Firefox metabugs]] | [[File:Firefox metabugs.png|1200px|Firefox metabugs]] | ||
=== How do I search for an already open regression? === | |||
Sometimes treeherder include alerts related to a test in the same summary, sometimes it doesn’t. To make sure that the regression you found doesn’t have already a bug open, you have to search in the current Firefox release meta-bug for regressions open with the summary similar to the summary of your alert. Usually, if the test name matches, it might be what you’re looking for. But, be careful, if the test name matches that doesn’t mean that it is what you’re looking for. You need to check it thoroughly.<br /> | |||
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). | |||