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

Issue 849837 link

Starred by 1 user
Status: Duplicate
Merged: issue 875899
Owner:
liaoyuke@chromium.org
Closed: Aug 30
Cc:
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 837855



Sign in to add a comment

Flake Detection: don't file bugs if Flake Analyzer has already filed one

Project Member Reported by liaoyuke@chromium.org, Jun 5 2018 
This is a little bit tricky because Flake Detection and Flake Analyzer have two different systems to file bugs, and it's hard to coordinate.

I think it makes sense to consolidate them into one, or potentially add Flake Analyzer's analysis results as a new type of flake occurrence to Flake Detection, and have Flake Detection file all the bugs, or the other way around.

Not blocking MVP, will think more after.

Comment 1 by st...@chromium.org, Jun 6 2018 

We need to unify them, otherwise we will cause some noises to developers
and sheriffs.

Comment 2 by st...@chromium.org, Jun 6 2018 

We should have code to look for an existing bug of the test.

Comment 3 by liaoyuke@chromium.org, Jun 6 2018 

Yep! I chatted with Jeff this morning, and the takeaway is that Flake Detection and Flake Analyzer should share the same Models and code to file bugs so that the filed bugs look consistent from developers' perspective. I'll explore more.

Comment 4 by liaoyuke@chromium.org, Aug 2

Labels: flake-detection

Comment 5 by liaoyuke@chromium.org, Aug 30

Mergedinto: 875899
Status: Duplicate (was: Assigned)
►

Sign in to add a comment