TestEngineering/Performance/Sheriffing/Alerts: Difference between revisions
< TestEngineering | Performance | Sheriffing
Jump to navigation
Jump to search
(Initial edit) |
(more about build metrics) |
||
| Line 1: | Line 1: | ||
= Perfherder alerts = | = Perfherder alerts = | ||
== General triage process == | |||
<how triaging is similar among all alerts> | |||
== Types of alerts == | == Types of alerts == | ||
| Line 5: | Line 8: | ||
=== Talos === | === Talos === | ||
* short description: [https://wiki.mozilla.org/index.php?title=Buildbot/Talos/Tests here] | * short description: [https://wiki.mozilla.org/index.php?title=Buildbot/Talos/Tests here] | ||
* frequency: daily, | * frequency: daily, little more than a dozen alerts | ||
* | * [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_coalescing coalesced] by SETA?: yes | ||
* available on platforms: | * available on platforms: | ||
** Linux 64bit (OPT | ** Linux: 64bit (OPT, PGO builds) | ||
** Windows 7 32bit, | ** Windows: 7 32bit, 10 64bit (OPT, PGO builds) | ||
** OS X 10.10 (OPT builds only) | ** OS X: 10.10 (OPT builds only) | ||
* | * triaging specifics: | ||
=== build_metrics === | === build_metrics === | ||
* short description: Monitor build times on multiple platforms, the size of the installers and other compiler-specific insights. | |||
* frequency: little less than daily, around 5 alerts | |||
* contact: :froydnj, :ted.mielczarek, :gps | |||
* [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_coalescing coalesced] by SETA?: no (doesn't require backfilling) | |||
* available on platforms: | |||
** Linux: 32/64bit (OPT, No-OPT builds) | |||
** Windows: 32/64bit (OPT, No-OPT, Mingw builds) | |||
** OS X: 10.10 (cross, no-cross builds) | |||
** Android: 4.0, 4.2, 5.0 | |||
* triaging specifics: | |||
** often easy to investigate | |||
** most alerts aren't noisy | |||
** when investigating, one should look for build config changes <ask :gps to provide more data> | |||
** 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 === | ||
=== AWSY === | === AWSY === | ||
=== platform_microbench === | === platform_microbench === | ||
Revision as of 08:31, 16 January 2018
Perfherder alerts
General triage process
<how triaging is similar among all alerts>
Types of alerts
Talos
- short description: here
- frequency: daily, little more than a dozen alerts
- coalesced by SETA?: yes
- available on platforms:
- Linux: 64bit (OPT, PGO builds)
- Windows: 7 32bit, 10 64bit (OPT, PGO builds)
- OS X: 10.10 (OPT builds only)
- triaging specifics:
build_metrics
- short description: Monitor build times on multiple platforms, the size of the installers and other compiler-specific insights.
- frequency: little less than daily, around 5 alerts
- contact: :froydnj, :ted.mielczarek, :gps
- coalesced by SETA?: no (doesn't require backfilling)
- available on platforms:
- Linux: 32/64bit (OPT, No-OPT builds)
- Windows: 32/64bit (OPT, No-OPT, Mingw builds)
- OS X: 10.10 (cross, no-cross builds)
- Android: 4.0, 4.2, 5.0
- triaging specifics:
- often easy to investigate
- most alerts aren't noisy
- when investigating, one should look for build config changes <ask :gps to provide more data>
- 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.