New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 613011 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Call out unusually long stage specifically, in ReportStage, in the case of timeout

Project Member Reported by akes...@chromium.org, May 18 2016

Issue description

We have a lot of canary timeouts. It would be nice if we made them easier to understand, for sheriffs. Eventually we'll have stuff in monarch, but in the meantime...

In ReportStage we already summarize historical per-stage times. Perhaps we can call out louder the specific stages that took unusually long?
https://uberchromegw.corp.google.com/i/chromeos/builders/auron_yuna-release/builds/35/steps/Report/logs/stdio

Or, have the stage itself realize that it took unusually long (via cidb query) and color itself yellow in the waterfall.
 
Owner: dgarr...@chromium.org

Comment 2 by autumn@chromium.org, May 23 2016

Labels: -current-issue
Status: Available (was: Untriaged)
Cc: semenzato@chromium.org
Status: WontFix (was: Available)
The stage performance stuff I added to ReportStage is going away in favor of Viceroy and related stats mechanisms. So... this goes away.

Sign in to add a comment