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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 05c6a56ccb00db1504d23d91728edc77037dee47
  bad_revision : 4270656328f068a1aeec3abd41fd0b31adc047b2

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame

Revision             Result                     N
chromium@511067      0.255494 +- 0.0304909      6        good
chromium@511107      0.370226 +- 0.27586        14       good
chromium@511124      0.370487 +- 0.217663       14       good
chromium@511125      ---                        ---      build failure
---                  ---                        ---      too many build failures to list
chromium@511146      0.409805 +- 0.223519       14       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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.