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

Issue 596222 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Limit auto-filed bugs from the lab to x / day

Project Member Reported by autumn@chromium.org, Mar 19 2016

Issue description

This idea came from a chat with Chrome Infra 

1. Establish baseline of 'average' # of bugs / day that are autofiled. 
2. Set limit to some about above average - once that many bugs are filed, don't file any more. 

Logic - we assume that if we are x above average, it's a widespread issue and it's not useful to file individual issues. 

 

Comment 1 by autumn@chromium.org, Mar 28 2016

Cc: -shuqianz@chromium.org
Owner: shuqianz@chromium.org
Status: WontFix (was: Untriaged)
This is a nice idea, but we have no central bug filing service (and no plan to implement one) that would know how many bugs had been filed in a given day, so it's not so easy to implement. I'd rather reduce our bug rate by better deduping and by turning off bug filing in many suites.

Comment 3 by autumn@chromium.org, Mar 30 2016

yes, this would only be implemented if we set up a central bug filing service https://bugs.chromium.org/p/chromium/issues/detail?id=596221 

I agree that de-duping and limiting which suites we alert on are the first things to do! 

de-duping bug is here 
Smarter de-duping: https://bugs.chromium.org/p/chromium/issues/detail?id=594301

Comment 4 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Sign in to add a comment