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

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


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

chromium-rel-win10

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/771
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/773
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Looking at the bisects, the startup test is not producing any output. That's bad, but when I went to triage I saw that the ref build moved too. So WontFix-ing because this is not a performance regression.

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