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

Issue 594300 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
█ fdeng@chromium.org
█ shuqianz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Smarter autofiled bugs: for widespread infra issues, autofiled bugs should be suppressed

Project Member Reported by autumn@chromium.org, Mar 12 2016 
Most of them failed with a message "[Errno 104] Connection reset by peer". This looks like some wide infra outage (maybe network issue) that affect all test. 

Sample issues: 
https://bugs.chromium.org/p/chromium/issues/detail?id=592980
https://bugs.chromium.org/p/chromium/issues/detail?id=592979
https://bugs.chromium.org/p/chromium/issues/detail?id=592977

Solution: be smarter about this: suppress or de-dupe bugs for infra failures. 

+Charlene / Fang to add more details.

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

Additional context from the email 
* One straightforward idea is to add a SuiteBug, file a suite-level bug if all tests in a suite failed due to the same reason.  Dedupe all later bugs to this one.
* Add a limit to the maxium number of comments we post to "SuiteBug", to avoid the flood.

Comment 2 by benhenry@google.com, Apr 26 2016

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

Comment 3 by akes...@chromium.org, Jun 13 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment