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

Issue 670382 link

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

Blocking:
issue 666097



Sign in to add a comment

Get rid of the in-memory state during analysis of flake

Project Member Reported by st...@chromium.org, Dec 1 2016 
Currently, we keep the state of analysis in memory and pass it over along the pipelines, and use it as part of the input to compute the next build number to rerun the test.

However, it's better to compute the next build number directly from the data points from all previous reruns.

This will make the code cleaner, and easier to test.

Comment 1 by chanli@chromium.org, Dec 6 2016

Cc: -chanli@chromium.org st...@chromium.org
Owner: chanli@chromium.org
Status: Started (was: Available)

Comment 4 by st...@chromium.org, Dec 9 2016

Blocking: 666097

Comment 5 by st...@chromium.org, Dec 9 2016

Labels: -Pri-2 Pri-1

Comment 6 by chanli@chromium.org, Dec 12 2016

Status: Fixed (was: Started)
►

Sign in to add a comment