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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=ee2ed9a1aaf11eae854a788301269ec9a42375db99ca49570486a68e5c6134bf


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Total:duration_avg/browse_news/browse_news_reddit

Revision             Result                  N
chromium@517335      16776.1 +- 1113.86      21      good
chromium@517382      16766.6 +- 889.715      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.reddit v8.runtimestats.browsing_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8961778528821150304


For feedback, file a bug with component Speed>Bisection

not reproducible