Now that builds are analyzed with multiple swarming tasks, it is no longer necessary for lookback_algorithm to manage how many iterations to rerun in case a stable build is suspected to be unreliable
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/fd9106d8b67130c5429a97e058de86f6ff89899b commit fd9106d8b67130c5429a97e058de86f6ff89899b Author: Jeffrey Li <lijeffrey@chromium.org> Date: Tue Sep 19 19:28:11 2017 [Findit] Flake Analyzer - Removing the concept of iterations_to_rerun from lookback_algorithm Bug: 765048 Change-Id: I4b94a953388769724e15da060dc51c779a204afc Reviewed-on: https://chromium-review.googlesource.com/668034 Commit-Queue: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Brandon Wylie <wylieb@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/test/lookback_algorithm_test.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/test/flake_analysis_util_test.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/lookback_algorithm.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/next_build_number_pipeline.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/recursive_flake_try_job_pipeline.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/test/next_build_number_pipeline_test.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/finish_build_analysis_pipeline.py [modify] https://crrev.com/fd9106d8b67130c5429a97e058de86f6ff89899b/appengine/findit/waterfall/flake/flake_analysis_util.py
Comment 1 by lijeffrey@chromium.org
, Sep 15 2017Labels: -Pri-3 Pri-1