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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/total:500ms_window:renderer_eqt:v8_max


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 v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

See #3.

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

This was timing out after a day, looks like someone tried to bisect on a summary metric but one of the pages was failing. I think in general we shouldn't be alerting on summary metrics like this, I can go change the sheriff config if that's ok.

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Mythri Alle
  Commit : 2d88095699f02011d0d0c7d21bf4f348ae453b20
  Date   : Wed Nov 22 11:48:27 2017
  Subject: Remove v8.browsing_desktop and v8.browsing_mobile benchmarks.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 30.95% | 834.500666667 -> 1092.76216667

Revision             Result                  N
chromium@518507      834.501 +- 15.4452      6      good
chromium@518559      849.098 +- 10.0483      6      good
chromium@518585      849.835 +- 22.4211      6      good
chromium@518598      847.162 +- 25.0389      6      good
chromium@518604      838.075 +- 37.6375      6      good
chromium@518607      849.188 +- 36.7217      9      good
chromium@518608      841.337 +- 25.7428      9      good
chromium@518609      1059.34 +- 272.751      9      bad       <--
chromium@518610      1092.76 +- 9.14138      6      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.pinterest.infinite.scroll v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection