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

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


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

android-nexus6
chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/mix_blend_mode_animation_hue.html

Revision             Result                  N
chromium@502934      20.73 +- 1.04603        21      good
chromium@503015      20.8741 +- 1.34228      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=mix.blend.mode.animation.hue.html 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/8967443829087278288


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.