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

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


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

android-nexus5X
android-one

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/css_value_type_length_simple.html?api_css_animations_N_0316

Revision             Result                   N
chromium@520204      21.6284 +- 0.890658      21      good
chromium@520294      21.8427 +- 5.24475       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=css.value.type.length.simple.html.api.css.animations.N.0316 smoothness.tough_animation_cases

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

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


For feedback, file a bug with component Speed>Bisection

Ref build stopped testing at same point. Looks like a measurement change.