Chromium Code Reviews| Index: tools/auto_bisect/bisect_results.py |
| diff --git a/tools/auto_bisect/bisect_results.py b/tools/auto_bisect/bisect_results.py |
| index 5c73d37c8caf9d31e0736932cac2408b9a801df3..c34cf89d54233d934e6dbc6e9099340b9edc3b42 100644 |
| --- a/tools/auto_bisect/bisect_results.py |
| +++ b/tools/auto_bisect/bisect_results.py |
| @@ -230,6 +230,13 @@ class BisectResults(object): |
| @staticmethod |
| def FindBreakingRevRange(revision_states): |
|
qyearsley
2015/01/16 18:37:03
I think it's probably worth it to add a test for t
RobertoCN
2015/01/30 21:23:32
Done.
|
| + """Finds the last known good and first known bad revisions. |
| + |
| + Note that since revision_states is expected to be in reverse cronological |
|
RobertoCN
2015/01/14 18:50:47
chronological not cronological.
RobertoCN
2015/01/30 21:23:32
Done.
|
| + order, the last known good revision is the first revision in the list that |
| + has the passed property set to 1, therefore the name |
| + `first_working_revision`. The inverse applies to `last_broken_revision`.\ |
|
RobertoCN
2015/01/14 18:50:47
Unnecessary backlash at the end of the line.(typo)
RobertoCN
2015/01/30 21:23:32
Done.
|
| + """ |
|
qyearsley
2015/01/16 18:37:03
[Optional] You could add Args and Returns sections
RobertoCN
2015/01/30 21:23:32
Done.
|
| first_working_revision = None |
| last_broken_revision = None |
|
qyearsley
2015/01/16 18:37:03
[Optional] It might be less confusing to reverse t
RobertoCN
2015/01/30 21:23:32
Acknowledged.
|
| @@ -287,10 +294,13 @@ class BisectResults(object): |
| [working_mean, broken_mean]) / |
| max(0.0001, min(mean_of_good_runs, mean_of_bad_runs))) * 100.0 |
| - # Give a "confidence" in the bisect. At the moment we use how distinct the |
| - # values are before and after the last broken revision, and how noisy the |
| - # overall graph is. |
| - confidence_params = (sum(working_means, []), sum(broken_means, [])) |
| + # Give a "confidence" in the bisect. Currently, we consider the values of |
| + # only the revisions at the breaking range (last known good and first known |
| + # bad) see the note in the docstring for FindBreakingRange. |
| + confidence_params = ( |
| + sum([first_working_rev.value['values']], []), |
| + sum([last_broken_rev.value['values']], []) |
| + ) |
| confidence = cls.ConfidenceScore(*confidence_params) |
| bad_greater_than_good = mean_of_bad_runs > mean_of_good_runs |