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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_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@505503      16.853 +- 0.264398       21      good
chromium@505519      16.8423 +- 0.335946      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --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/8966091821696952288


For feedback, file a bug with component Speed>Bisection

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