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

Issue 800411 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Exonerator: Track metric for avoidable-user-action

Project Member Reported by pprabhu@chromium.org, Jan 9 2018

Issue description

In the CQ exonerator, start tracking CLs that exonerator decided to exonerate, but where the user had already taken the exact action that exonerator was going to take -- i.e., marke CQ:+1.
This shouldn't include other user actions like a new patch set.

This metric is one way of measuring user impatience with the CQ, and as our CQ becomes more responsive and trusted, this metric should fall (people won't be in the habit of hitting CQ:+1 on failures, and only exonerator will exonerate CLs based on more knowledge than the average user)
 

Comment 1 by xixuan@chromium.org, Jan 11 2018

Owner: pho...@chromium.org
Assign to @phobbs, to let him decide whether it's a fix-it bug.

Comment 2 by pho...@chromium.org, Jan 11 2018

Blockedon: 790742
Status: Assigned (was: Untriaged)
This is a useful idea, but it's blocked on getting ts-mon working in GAE Flex. There's a "gae_ts_mon" library which works in the GAE Standard environment, but it relies on the Standard-only Datastore ORM to synchronize across instances.

Comment 3 by pho...@chromium.org, Mar 29 2018

Cc: nxia@chromium.org
Labels: CL-Exonerator
Blockedon: -790742

Comment 5 by pho...@chromium.org, Apr 21 2018

Status: fix (was: Assigned)

Comment 6 by pho...@chromium.org, Apr 21 2018

Status: Fixed (was: Fix)

Sign in to add a comment