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

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


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

chromium-rel-win7-gpu-ati

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385875         18.164866   0.210401    18          good
chromium@385899         18.194713   0.139964    18          bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 602317

Test Command: .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu
Test Metric: TabCapturePerformance_comp_gpu_novsync/CaptureSucceeded
Relative Change: 0.32%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1317
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015660811292099184


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=602317

| 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 Tests>AutoBisect.  Thank you!

re-kicked bisect with modified range.

re-kicked with a wider range

This has recovered.

Marking as fixed as per #5