Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976081254094630592

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: bf76fd9adfb3e875144b070fba3415d8e592baf8
  bad_revision : 021a340142453876a5a7ab92e90295cb176163ee

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : GC:duration_avg/browse_social/browse_social_twitter
  Change       : 316.11% | 9.71283333333 -> 40.4158333333

Revision             Result                  N
chromium@480804      9.71283 +- 19.4697      6      good
chromium@480813      9.37783 +- 20.4261      6      good
chromium@480818      13.3557 +- 24.1395      6      good
chromium@480822      40.4158 +- 11.3998      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976081254094630592

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5757210149257216


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975898305729848240

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 185c7229bb3544d70589a8a084b4e14e73efddc2
  bad_revision : 021a340142453876a5a7ab92e90295cb176163ee

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : GC:duration_avg/browse_social/browse_social_twitter
  Change       : 209.27% | 12.2135 -> 37.7731666667

Revision             Result                  N
chromium@480804      12.2135 +- 19.7504      6      good
chromium@480813      10.7623 +- 16.3585      6      good
chromium@480822      37.7732 +- 11.1196      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8975898305729848240

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5757210149257216


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!