160
edits
TestEngineering/Performance/Sheriffing/Alerts: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Alerts (view source)
Revision as of 09:29, 16 January 2018
, 16 January 2018mention Bob
(more Autophone details) |
(mention Bob) |
||
| Line 33: | Line 33: | ||
* short description: <provide it> | * short description: <provide it> | ||
* frequency: every week or so, around 4 alerts | * frequency: every week or so, around 4 alerts | ||
* contact: | * contact: :bc: | ||
* [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_coalescing coalesced] by SETA?: no | * [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_coalescing coalesced] by SETA?: no | ||
* available on platforms: | * available on platforms: | ||
| Line 40: | Line 40: | ||
** when investigating, one should look for Android related changes | ** when investigating, one should look for Android related changes | ||
** many of these tests are pretty noisy; often, they turn out to be invalid (one reason is devices overheat, which affects tests) | ** many of these tests are pretty noisy; often, they turn out to be invalid (one reason is devices overheat, which affects tests) | ||
** should consider to needinfo? | ** should consider to needinfo? :bc:, to check status of suspect phone devices | ||
** tricky to investigate; | ** tricky to investigate; consider using also [http://phonedash.mozilla.org/ Phonedash], as it's a more precise investigation tool for mobile regressions | ||
** retriggers are almost always needed, but results show up after a day or so | ** retriggers are almost always needed, but results show up after a day or so | ||
=== AWSY === | === AWSY === | ||