Support manually kicking off a flake analysis at a given revision range for a given flaky tset |
|||||||||
Issue descriptionManually we could do that through buildbucket, but it's better to kick it off through Findit. The best approach is to kick off from the analysis result page, so that the data point could be added automatically there.
,
Apr 25 2017
,
Apr 25 2017
Input: on /waterfall/flake?key=KEY****, lower-bound commit position, upper-bound commit position, ndb.Key.url_safe of an existing analysis. Backend: determine the closest build cycle for the upper-bound or lower-bound commit positions automatically.
,
Apr 25 2017
Jeff: please create sub-bugs for this big bug.
,
Apr 25 2017
,
Apr 25 2017
,
Apr 25 2017
,
May 8 2017
,
May 8 2017
,
May 15 2017
,
May 15 2017
,
Jun 26 2017
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by st...@chromium.org
, Mar 30 2017