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

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


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

android-nexus5X
android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Compile:duration_avg/browse_social/browse_social_tumblr_infinite_scroll

Revision             Result                  N
chromium@497647      1095.9 +- 526.873       21      good
chromium@497657      1086.19 +- 467.005      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.social.tumblr.infinite.scroll 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/8970027930567112912


For feedback, file a bug with component Speed>Bisection

not repruducible