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

Issue 799324 link

Starred by 1 user
Status: Fixed
Owner:
lijeffrey@chromium.org
Closed: Jun 2018
Cc:
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 782434



Sign in to add a comment

[Findit] Flake Analyzer - Deprecate suspected flake build number in favor of ID once switched

Project Member Reported by lijeffrey@chromium.org, Jan 5 2018 
Eventually build IDs will be strings instead of numbers. Once this switch is made in luci the field "suspected_flake_build_number" in MasterFlakeAnalysis will have no meaning. Use suspected_flake_build_id instead.

Comment 1 by lijeffrey@chromium.org, Jan 5 2018

Components: Tools>Test>FindIt>Flakiness
Owner: lijeffrey@chromium.org
Status: Assigned (was: Assi)
No action yet until switch is made in LUCI.

Comment 2 by st...@chromium.org, Jan 5 2018 

I think we could get rid of it, and replace with a regression range which is being shrinked along the way.

Comment 3 by lijeffrey@chromium.org, Jan 5 2018

Blocking: 782434
Regression range can be calculated in realtime based on datapoints, no need to store it explicitly?

Comment 4 by lijeffrey@chromium.org, Jun 14 2018

Status: Fixed (was: Assigned)
►

Sign in to add a comment