stddev bisect doesn't work |
|||
Issue descriptionexample: https://bugs.chromium.org/p/chromium/issues/detail?id=596817#c7 It bails out early even though the stddev was 2 in the first run and 84 in the second.
,
Mar 29 2016
What's a stddev bisect?
,
Mar 29 2016
By default, the bisect dialog on the dashboard bisects the "mean" (probably not quite correct with the new classification algorithm). But it has a return code option, and also a std_dev option. The latter used to bisect on increased noise. See the blocked bug for example use case.
,
Mar 29 2016
It doesn't make sense to have the distinction with the new classification algorithm.
,
Mar 29 2016
It sounds like there is another bug with the bisect in https://bugs.chromium.org/p/chromium/issues/detail?id=596817#c7 ? I'm okay with fixing that and removing the UI for std_dev bisect in the dialog, as long as the use case is still met. It might be better to file a blocking bug for 596817 that is specifically about the bisect issues though.
,
Feb 3 2017
,
Feb 6 2017
This is an old-ish auto-bisect bugs. This might be fixed with Pinpoint, or it's not going to get fixed. If you disagree with me, please reopen the bug and mark it "Untriaged". |
|||
►
Sign in to add a comment |
|||
Comment 1 by sullivan@chromium.org
, Mar 29 2016