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

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


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

android-nexus5X

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

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

Hi bshe@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 : Biao She
  Commit : 75f62492270810ec386855c6c33a773cc6a54a30
  Date   : Thu Nov 16 18:44:17 2017
  Subject: Update GVR to 1.101.1

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_googleplus.html
  Change       : 0.63% | 29.3613571429 -> 29.5292857143

Revision             Result                   N
chromium@517073      29.3614 +- 0.272337      14      good
chromium@517106      29.3427 +- 0.106646      6       good
chromium@517123      29.3532 +- 0.219805      14      good
chromium@517131      29.3561 +- 0.351653      21      good
chromium@517135      29.3412 +- 0.100463      6       good
chromium@517136      29.5108 +- 0.38619       6       bad       <--
chromium@517137      29.5182 +- 0.322863      6       bad
chromium@517139      29.5293 +- 0.601441      14      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=file...static.top.25.googleplus.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection

This looks like a very small regression which has since recovered at:

Point ID: 517689
Time added: 2017-11-18T06:47:51.000Z

I think it's ok to close as WontFix.

wontfix per comment 4. Thanks!