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

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


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

android-webview-nexus5X

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

=== Auto-CCing suspected CL author herb@google.com ===

Hi herb@google.com, 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 : Herb Derby
  Commit : 0f68a2d3dfaeef91796c0e7e3f5e92a1d949ad2b
  Date   : Thu Sep 14 22:38:06 2017
  Subject: Use Skia's faster blur code.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_google.html
  Change       : 2.36% | 40.7616666667 -> 39.729

Revision             Result                   N
chromium@502016      40.7617 +- 0.851693      6      good
chromium@502031      40.5416 +- 1.10196       9      good
chromium@502039      40.7507 +- 0.705369      9      good
chromium@502043      40.508 +- 1.21232        9      good
chromium@502045      40.9052 +- 1.06253       6      good
chromium@502046      39.729 +- 0.897218       9      bad       <--

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=file...static.top.25.google.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/8968030732673485760


For feedback, file a bug with component Speed>Bisection

I don't think this is me. It looks like the bisect found a 2% change, and it was faster. Thank you for recognizing me.

Looking at the graphs, it does look like a bad jump. But, most of the graphs fall back down a little later. Could this be a change in your testing environment?

Unable to triage this issue from TE-end, hence adding TE-NeedsTriageHelp for further triage.

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

Most of these alerts have recovered, except: ChromiumPerf/android-webview-nexus5X/rasterize_and_record_micro.top_25 / rasterize_time / file___static_top_25_google.html

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_youtube.html

Revision             Result                   N
chromium@501500      58.9905 +- 0.416134      6      good
chromium@503000      59.7362 +- 0.235476      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=file...static.top.25.youtube.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/8967482190921057344


For feedback, file a bug with component Speed>Bisection

 Issue 768538  has been merged into this issue.

WontFix since this is several months old and we haven't had a successful bisect.