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

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


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

android-nexus5
android-nexus5X
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-high-dpi

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

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

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


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_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.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/8962786563771409952


For feedback, file a bug with component Speed>Bisection

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

This failed because none of the runs produced the metric being bisected. It's a summary metric I believe, and since there's a failing page it's not being produced. I tried kicking this off on another metric for a specific page.

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

Suspected Commit
  Author : Nghia Nguyen
  Commit : 564e33d345ee080be36ad0e6b6107afbcd09df4d
  Date   : Tue Nov 07 14:06:23 2017
  Subject: Update wprgo binaries to latest version

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Parse:duration_avg/browse_news/browse_news_reddit
  Change       : 3.20% | 269.024333333 -> 277.630333333

Revision                                 Result                  N
chromium@515085                          269.024 +- 6.74727      6       good
chromium@515123                          269.525 +- 10.0986      9       good
chromium@515142                          269.371 +- 6.54157      9       good
chromium@515147                          270.0 +- 19.6455        14      good
chromium@515148                          268.631 +- 2.61587      6       good
chromium@515148,catapult@a7fb6add75      268.159 +- 3.64782      6       good
chromium@515148,catapult@b33d83ad5d      268.828 +- 4.45252      6       good
chromium@515148,catapult@564e33d345      277.795 +- 8.07244      6       bad       <--
chromium@515148,catapult@c169bba255      278.937 +- 13.5029      6       bad
chromium@515149                          280.556 +- 11.8145      6       bad
chromium@515151                          278.307 +- 11.1805      9       bad
chromium@515160                          277.63 +- 10.4858       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.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/8962288645495885104


For feedback, file a bug with component Speed>Bisection