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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : V8 C++:duration_avg/browse_news/browse_news_qq

Revision             Result                  N
chromium@459396      802.898 +- 67.3533      21      good
chromium@459450      811.35 +- 80.7951       21      bad

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

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

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


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

I think that was a flake.