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

Issue 726210 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

[Findit] Flake analyzer - Filter runtime analysis points by upper/lower bounds

Project Member Reported by lijeffrey@chromium.org, May 25 2017

Issue description

MaserFlakeAnalysis has only a single list of data points which is passed to the various pipelines for determining the next run point number.

Since we will support running a specific range and the lookback algorithm consumes the full list of data points, it is possible the lookback algorithm to suggest the next run point outside of the range.

During rerun, the data points should not necessarily be tied to already run data points.
 
Summary: [Findit] Flake analyzer - Filter runtime analysis points by upper/lower bounds (was: [Findit] Flake analyzer - use separate data point list during run time)
A better solution is to allow filtering by upper/lower bounds, this way the same data_points can be reused without having to keep track of two separate lists of points, one of which is a subset of the other.
Project Member

Comment 2 by bugdroid1@chromium.org, May 30 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/e37b41dee441781178ff22e9e1b51e646d0b5e28

commit e37b41dee441781178ff22e9e1b51e646d0b5e28
Author: Jeffrey Li <lijeffrey@chromium.org>
Date: Tue May 30 20:30:26 2017

[Findit] Flake Analyzer - Filter data points by upper/lower bounds

Bug:  726210 
Change-Id: If098699c26afce1e756a8d52205c52dc8745d3bd
Reviewed-on: https://chromium-review.googlesource.com/514512
Reviewed-by: Chan Li <chanli@chromium.org>
Reviewed-by: Roberto Carrillo <robertocn@chromium.org>
Commit-Queue: Jeffrey Li <lijeffrey@chromium.org>

[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/flake/test/recursive_flake_pipeline_test.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/process_flake_swarming_task_result_pipeline.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/flake/recursive_flake_pipeline.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/flake/process_flake_try_job_result_pipeline.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/model/flake/master_flake_analysis.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/flake/recursive_flake_try_job_pipeline.py
[modify] https://crrev.com/e37b41dee441781178ff22e9e1b51e646d0b5e28/appengine/findit/waterfall/flake/test/recursive_flake_try_job_pipeline_test.py

Status: Fixed (was: Started)

Sign in to add a comment