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

Issue 849826 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 845581



Sign in to add a comment

Make sure a flake is still active before filing bugs

Project Member Reported by liaoyuke@chromium.org, Jun 5 2018

Issue description

Due to the limit that Flake Detection should not file more than 10 bugs a day, there could be a significant delay between the flakes were active and the bug is filed. For example:

between 12:00pm and 1:00pm, a test is flaky and has 10 occurrences, however, due to the limitation, a bug is not filed; An hour later, the test is fixed and the flakes are gone at around 2:00pm; 20 hours later, Flake Detection is allowed to file new bugs, so it files a bug for this test. However, it shouldn't because the test is already fixed and is not active anymore.

One simple trick we can do is that, before filing a bug, make sure that there is at least one flake within the past 2 hours. (2 hours is just an example, this time needs to be adjusted according to the delay of flake detection).
 

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

As we are working on the new flake detection, this seems a good timing to re-evaluate this limitation. You may talk to sergiyb@ on how that limitation was chosen.
Discussed offline, but still reply here for the record. Increasing the bug limit (is 10) solves the problem, but might be risky. So a better short term solution would be to verify there is an occurrence in the most recent few hours.
Status: Fixed (was: Assigned)

Sign in to add a comment