Confirmed users
3,376
edits
Buildbot/Talos/Sheriffing: Difference between revisions
→Backout: fixed links
(→Finding the root cause: - more data) |
(→Backout: fixed links) |
||
| Line 31: | Line 31: | ||
Here is an example of a backout which affected many tests. | Here is an example of a backout which affected many tests. | ||
[[ | [[http://alertmanager.allizom.org:8080/alerts.html?rev=d4c4897f9ffb AlertManager]] [[http://alertmanager.allizom.org:8080/alerts.html?rev=5cc96a763c3f related coalesced]] | ||
This example is interesting because we see one change which was quickly identified as the correct change, but one job was coalesced. The coalescing is easy to detect because looking at the suspected [[http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f4eea7e2f94b&tochange=5cc96a763c3f changeset]] it is a range. That range includes our backed out changeset as well as the graph showing the backout pattern. Adding more to it, this is on Windows 8 which is the platform which showed a regression on the backout. We have high confidence to map this coalesced alert as being the root cause of the backout. | This example is interesting because we see one change which was quickly identified as the correct change, but one job was coalesced. The coalescing is easy to detect because looking at the suspected [[http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f4eea7e2f94b&tochange=5cc96a763c3f changeset]] it is a range. That range includes our backed out changeset as well as the graph showing the backout pattern. Adding more to it, this is on Windows 8 which is the platform which showed a regression on the backout. We have high confidence to map this coalesced alert as being the root cause of the backout. | ||