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

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


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

android-nexus5X
chromium-rel-win7-gpu-ati

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

=== 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_path.html?api_css_animations_N_0316

Revision             Result                  N
chromium@494432      23.8392 +- 15.3769      21      good
chromium@494567      26.1752 +- 22.2963      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.path.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/8969913026313110976


For feedback, file a bug with component Speed>Bisection

One of these has the ref build moving too, other is in the noise.