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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglsH6kAoM


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : hans
  Commit : ba2ff9ad0d643a443575c839e56ae9edf7106643
  Date   : Mon Jun 05 02:02:06 2017
  Subject: Revert of "win: Set is_clang=true by default over the weekend."

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/frame_times
  Change       : 2.97% | 18.743812844 -> 19.3005342847

Revision             Result                    N
chromium@476914      18.7438 +- 0.0199757      6      good
chromium@476918      18.7417 +- 0.0238491      6      good
chromium@476920      18.7464 +- 0.0372781      6      good
chromium@476921      19.2948 +- 0.0139384      6      bad       <--
chromium@476927      19.2997 +- 0.0136923      6      bad
chromium@476940      19.3005 +- 0.0249308      6      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 smoothness.tough_animation_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977001755471367408

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5689749517369344


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!