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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/IE Chalkboard

Revision             Result                  N
chromium@520204      93.5365 +- 93.0919      21      good
chromium@520294      93.7229 +- 73.7097      21      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=IE.Chalkboard smoothness.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection

Closing.  Ref build moved.