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

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


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

android-nexus5X

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

=== 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    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/Pinterest


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=Pinterest smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Trying bisects on some of the windows machines (which are hopefully more stable) over a wider range, since the graphs ramp up.

=== Auto-CCing suspected CL author wkorman@chromium.org ===

Hi wkorman@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Walter Korman
  Commit : 7d7ff538f2290ac340336b14c34ba6183566dd3c
  Date   : Wed Aug 16 23:09:50 2017
  Subject: Migrate top_25 and top_25_smooth PageSet(s) to WprGo.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/ESPN
  Change       : 10.51% | 14.7021666667 -> 16.2476666667

Revision             Result                   N
chromium@494708      14.7022 +- 0.604123      6      good
chromium@494937      14.7785 +- 0.804934      6      good
chromium@494966      14.4655 +- 1.29212       6      good
chromium@494980      14.5153 +- 1.15364       6      good
chromium@494987      14.6177 +- 0.700569      6      good
chromium@494989      14.8003 +- 0.838402      6      good
chromium@494990      16.4097 +- 0.835565      6      bad       <--
chromium@494991      16.7537 +- 1.86125       6      bad
chromium@494994      16.4228 +- 1.02743       6      bad
chromium@495051      16.3458 +- 1.70761       6      bad
chromium@495165      16.2477 +- 1.16087       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=ESPN smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : Walter Korman
  Commit : 7d7ff538f2290ac340336b14c34ba6183566dd3c
  Date   : Wed Aug 16 23:09:50 2017
  Subject: Migrate top_25 and top_25_smooth PageSet(s) to WprGo.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/ESPN
  Change       : 13.83% | 14.5416666667 -> 16.5535

Revision             Result                  N
chromium@494404      14.5417 +- 1.69866      6      good
chromium@494790      13.798 +- 0.759978      6      good
chromium@494983      14.1551 +- 2.31152      9      good
chromium@494989      14.2817 +- 4.22834      9      good
chromium@494990      16.0758 +- 2.64476      9      bad       <--
chromium@494991      16.1482 +- 2.95755      9      bad
chromium@494992      16.3064 +- 2.28529      9      bad
chromium@494995      16.2962 +- 4.50483      9      bad
chromium@495007      16.3224 +- 2.45771      9      bad
chromium@495031      16.335 +- 1.22475       6      bad
chromium@495079      15.8579 +- 2.3483       9      bad
chromium@495175      16.5535 +- 2.09936      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=ESPN smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

This is essentially a known new baseline, itself now replaced due to switch to static pages.

History in brief:

Pinterest page was essentially broken prior to this, see  issue 757601 .

It was re-recorded in the WPRGo archive Sep 2 in:

https://chromium.googlesource.com/chromium/src/+/71d0b6e55036e66e74dde48b1c7d5364eb1e5b1d

We moved to a new static page set Sep 7 in:

https://chromium.googlesource.com/chromium/src/+/2a87e954ef8849a96627048487928b381d4b37ed