All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=729586

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxuT6rwsM


Bot(s) for this bug's original alert(s):

android-webview-nexus6

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

=== 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: a19c77077f663f771e822ffb025d9cc607e9cf8e
  bad_revision : 582f3d53c92a020931828dc67e6a849db4f56f93

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       : IC:duration_avg/browse_social/browse_social_instagram
  Change       : 14.12% | 653.090666667 -> 745.3115

Revision             Result                  N
chromium@476632      653.091 +- 25.5024      6      good
chromium@476647      661.987 +- 29.4532      6      good
chromium@476661      745.311 +- 57.2024      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.instagram v8.runtimestats.browsing_mobile

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

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


| 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/8977430904498802832

Blocking on crbug.com/731142 for the bot going purple while running tests.

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

Please try rerunning the bisect.


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       : IC:duration_avg/browse_social/browse_social_instagram
  Change       : 12.31% | 650.242 -> 730.259333333

Revision                           Result                  N
chromium@476632                    650.242 +- 36.8143      6      good
chromium@476647                    655.871 +- 21.1327      6      good
chromium@476654                    662.024 +- 28.2674      6      good
chromium@476656                    666.067 +- 30.7794      9      good
chromium@476656,v8@502c6ae6a0      728.021 +- 63.487       6      bad
chromium@476656,v8@3b7ff7a5e5      727.864 +- 68.9376      6      bad
chromium@476657                    728.362 +- 89.1378      9      bad
chromium@476658                    749.771 +- 55.032       6      bad
chromium@476661                    730.259 +- 62.4637      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.instagram v8.runtimestats.browsing_mobile

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

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


| 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!

Recovered since then.