Issue 851546 link

Starred by 1 user

Issue metadata

Status:	Available
Owner:	----
Cc:	seanmccullough@chromium.org zhangtiff@chromium.org
Components:	Infra>Sheriffing>SheriffOMatic
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	2
Type:	Bug
Milestone-Data

Sheriff-o-matic giving incorrect # of revisions since problem started occurring

Project Member Reported by charliea@chromium.org, Jun 11 2018

Issue description

I'm looking at an infrastructure failure right now where SOM seems to be giving a hugely inaccurate # of revisions since the problem started occuring.

In som.png, you can see that Sheriff-o-matic is saying that the problem has been occurring for the past 25 revisions.

In milo.png, you can see that in fact, this is the first time that the problem has occurred.

SOM team, any idea what's going on here?

	som.png 37.7 KB View Download

	milo.png 452 KB View Download

Comment 1 by zhangtiff@chromium.org, Jun 16 2018

Labels: Milestone-Data

Not sure what's happening here. It looks like hte failure_count is based on suntracting the id of the first build from the last build: https://cs.chromium.org/chromium/infra/go/src/infra/appengine/sheriff-o-matic/frontend/elements/som-extension-build-failure/som-extension-build-failure.js?type=cs&q=since+first+detection+file:%5Einfra/go/src/infra/appengine/sheriff-o-matic/+package:%5Echromium$&g=0&l=62

Comment 2 by seanmccullough@chromium.org, Dec 18

Status: Available (was: Untriaged)

The first and last build are determined by the analyzer when it generates the alert, which is where the underlying problem probably is.

►

Issue 851546 link

Issue metadata

Sheriff-o-matic giving incorrect # of revisions since problem started occurring

Issue description

Comment 1 by zhangtiff@chromium.org, Jun 16 2018

Comment 1 Deleted

Comment 2 by seanmccullough@chromium.org, Dec 18

Comment 2 Deleted

Sign in to add a comment