GetCompatibleCommand checks chromium revision to set appropriate browser type.
While processing 3rd party repositories by bisect, it was trying to compare dependency module
revision instead of chromium revision.
BUG=388411
NOTRY=true
Review URL: https://codereview.chromium.org/414893002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285103 0039d316-1c4b-4281-b951-d872f2087c98
Prior to crrev.com/274857 *only* android-chromium-testshell. Then until crrev.com/276628 *both* (android-chromium-testshell and
android-chrome-shell) work. After that rev 276628 *only* android-chrome-shell works. bisect-perf-reggresion.py script should
handle these cases and set appropriate browser type based on revision.
BUG=385324
NOTRY=true
Review URL: https://codereview.chromium.org/399463002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283308 0039d316-1c4b-4281-b951-d872f2087c98
Make bisects to look for the pattern RESULT lines with {mean, stddev} format while parsing results log.
BUG=366431
NOTRY=true
Review URL: https://codereview.chromium.org/288843002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270788 0039d316-1c4b-4281-b951-d872f2087c98
NOTRY=true
BUG=366392
Bisect could not reproduce a change in the not/valid metric.
Confidence in Bisection Results: 0%
To reproduce locally:
$ echo android-chrome
Tested commits:
Depot Commit SHA Mean Std. Error State
android-chrome 0000000000000000000000000000000000000000 1.00 +-0.00
chromium 0000000000000000000000000000000000000000 0.00 +-0.00
chromium http://src.chromium.org/viewvc/chrome?view=revision&revision=265919 0.00 +-0.00
chromium http://src.chromium.org/viewvc/chrome?view=revision&revision=265917 0.00 +-0.00
chromium http://src.chromium.org/viewvc/chrome?view=revision&revision=265912 0.00 +-0.00
chromium http://src.chromium.org/viewvc/chrome?view=revision&revision=265904 0.00 +-0.00
android-chrome 0000000000000000000000000000000000000000 0.00 +-0.00
Average build time : 0:00:00
Average test time : 0:00:00
WARNINGS:
!!! Due to build errors, regression range could not be narrowed down to a single commit.
!!! Tests were only set to run once. This may be insufficient to get meaningful results.
!!! Confidence is 0%. Try bisecting again on another platform, with increased repeat_count or on a sub-metric that shows the regression more clearly.
Review URL: https://codereview.chromium.org/256593004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266322 0039d316-1c4b-4281-b951-d872f2087c98
Goal: To make it clearer how percentage change is calculated, and make it so that it's the same as how the dashboard calculates it.
BUG=
Review URL: https://codereview.chromium.org/241273002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265791 0039d316-1c4b-4281-b951-d872f2087c98
This version is a little bit different from the last; main differences:
- I saw that the "CalculateBounds" was returning the minimum and maximum of the means of the input list, so I thought it would be easier to understand if this was done by mapping CalculateMean and then directly making a tuple with min/max.
- Since CalculateTruncatedMean(xs, 0) is just the mean, and this is used in several place, I extracted out a convenience function CalculateMean.
- CalculateConfidence doesn't refer to self, so I thought it was reasonable to move it up to be a top-level function with the other stats functions.
BUG=
Review URL: https://codereview.chromium.org/220113012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@262924 0039d316-1c4b-4281-b951-d872f2087c98
