160
edits
TestEngineering/Performance/Sheriffing/Alerts: Difference between revisions
TestEngineering/Performance/Sheriffing/Alerts (view source)
Revision as of 09:18, 16 January 2018
, 16 January 2018more Autophone details
(platform_microbench description) |
(more Autophone details) |
||
| Line 17: | Line 17: | ||
=== build_metrics === | === build_metrics === | ||
* short description: Monitor build times on multiple platforms, the size of the installers and other compiler-specific insights. | * short description: Monitor build times on multiple platforms, the size of the installers and other compiler-specific insights. | ||
* frequency: | * frequency: every 1-2 days, around 5 alerts | ||
* contact: :froydnj, :ted.mielczarek, :gps | * contact: :froydnj, :ted.mielczarek, :gps | ||
* [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 (shouldn't require backfilling) | ||
* available on platforms: | * available on platforms: | ||
** Windows: 32/64bit (OPT, No-OPT, Mingw builds) | ** Windows: 32/64bit (OPT, No-OPT, Mingw builds) | ||
| Line 31: | Line 31: | ||
** build times often spike upwards for just a short time; they then lower to previous levels thanks to caching mechanisms set in place. We mark these as invalid alerts. | ** build times often spike upwards for just a short time; they then lower to previous levels thanks to caching mechanisms set in place. We mark these as invalid alerts. | ||
=== Autophone === | === Autophone === | ||
* short description: <provide it> | |||
* frequency: every week or so, around 4 alerts | |||
* contact: <mention Bob Clary> | |||
* [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_coalescing coalesced] by SETA?: no | |||
* available on platforms: | |||
** Android: 4.2, 4.4, 6.0, 7.1 | |||
* triaging specifics: | |||
** 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) | |||
** should consider to needinfo? Bob Clary, to check status of suspect phone devices | |||
** tricky to investigate; should use Phonedash, as a more precise investigation tool | |||
** retriggers are almost always needed, but results show up after a day or so | |||
=== AWSY === | === AWSY === | ||
* short description: <provide it> [https://wiki.mozilla.org/AWSY/Tests link] | * short description: <provide it> [https://wiki.mozilla.org/AWSY/Tests link] | ||