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

Issue 598509 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 596817



Sign in to add a comment

stddev bisect doesn't work

Project Member Reported by sullivan@chromium.org, Mar 29 2016

Issue description

example: 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.
 
Blocking: 596817

Comment 2 by dtu@chromium.org, Mar 29 2016

What's a stddev bisect?
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.

Comment 4 by dtu@chromium.org, Mar 29 2016

It doesn't make sense to have the distinction with the new classification algorithm.
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.
Components: Speed>Bisection
Status: WontFix (was: Unconfirmed)
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