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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-latency-mark-compactor_avg/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@460623      44.6202 +- 157.098      21      good
chromium@460650      51.0747 +- 139.576      21      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.news.nytimes v8.runtimestats.browsing_mobile_classic

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

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


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

The regression happens on one device/webpage and is not reproducible on bot.