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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6MXi_wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6Mao5wkM


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

android-webview-nexus5X
android-webview-nexus6

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

The frame_times metric regressed on other tests along with the reference. The regressions in this bug don't have a reference. Just making sure the bisect bot comes back saying it couldn't reproduce.

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

Hi senorblanco@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 : senorblanco
  Commit : 0ad079ddaea6dedf8656bf374b5c0cd8a601da98
  Date   : Tue Feb 07 22:29:37 2017
  Subject: Add MotionMark's <canvas> fill and stroke tests to telemetry.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/frame_times
  Change       : 52.64% | 43.6719489571 -> 66.6593458298

Revision             Result                  N
chromium@448719      43.6719 +- 10.5444      6      good
chromium@448736      46.9381 +- 8.87659      6      good
chromium@448744      46.5757 +- 8.46734      6      good
chromium@448745      46.2606 +- 9.6347       6      good
chromium@448746      63.8151 +- 12.8537      6      bad       <--
chromium@448748      64.5432 +- 12.4189      6      bad
chromium@448752      66.6593 +- 11.0343      6      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 smoothness.tough_path_rendering_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988098591515319776

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5776162518728704


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

This is expected, since I added new tests which affected the overall score.