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

Issue 677590 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

CQ reliability dashboard in viceroy

Project Member Reported by katthomas@chromium.org, Dec 30 2016

Issue description

We want to create a place where chrome devs can go when they're wondering "What's up with the CQ?"

We'll start with cycle time and false rejection graphs for now, and can add more later as we learn what is useful for developers.

This is not intended to be a reference point for trouble shooting CQ issues.
 
Status: Fixed (was: Started)
Status: Started (was: Fixed)
Reopening this until it has been tuned and communicated w/ Chrome developers.
Blocking: -636614
Labels: CQ-Reliability-and-Performance
We should make the false rejections graph default to a longer duration if possible. W/ just one day it shows too little data. 
Components: Infra>Monitoring
Cc: -andyb...@chromium.org
Some more modifications:

* Add blink graphs
* Fix the windows: 1h w/ shorter duration, 224h w/ longer duration
* Update the wording to be more specific
* Add monitoring + graph for the distribution of duration of unfinished jobs sampled at a regular interval and graph those amounts to communicate "How long is the CQ taking right now?" 



Project Member

Comment 9 by bugdroid1@chromium.org, Feb 6 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/388499965d6855d6ac3b88aefce9abaeab2ecf24

commit 388499965d6855d6ac3b88aefce9abaeab2ecf24
Author: Katie Thomas <katthomas@google.com>
Date: Mon Feb 06 22:10:22 2017

Status: Fixed (was: Started)

Sign in to add a comment