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

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


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

chromium-rel-win7-dual

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6934
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/9001344034060611824

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6934
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/9001253427582486512

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6937
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/9000592706937146128

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/495
Failure reason: the build has failed due to infrastructure failure.

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@418812  129.861  2.50665  5  good
chromium@418819  117.813  18.9329  5  good
chromium@418822  121.596  11.9976  5  good
chromium@418823  862.67   170.658  5  bad
chromium@418824  913.539  97.5052  5  bad
chromium@418825  850.924  190.084  5  bad
chromium@418838  830.991  174.822  5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 647605

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.typical_25
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___www.flickr.com_search_?q_monkeys_f_hp
Relative Change: 539.91%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2207
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000461762642846432


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

| 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!

Ned, this bisect is pointing at the catapult roll with just https://codereview.chromium.org/2341723004 (Revert of "[telemetry] Wire TsProxy through telemetry's network stack.")

If this is pointing to a revert, is ti a real thing?

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

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

Suspected Commit
  Author : perezju
  Commit : 3cc40b37372927435ed69f91aec2117488b0825c
  Date   : Thu Sep 15 09:25:34 2016
  Subject: Revert of "[telemetry] Wire TsProxy through telemetry's network stack." (patchset #1 id:1 of https://codereview.chromium.org/2335403003/ )

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.html5rocks.com_en_
  Change       : 187.50% | 336.666833333 -> 967.913

Revision                                 Result                  N
chromium@418812                          336.667 +- 33.4184      6      good
chromium@418820                          280.703 +- 30.8082      6      good
chromium@418822                          287.879 +- 36.508       6      good
chromium@418822,catapult@3cc40b3737      982.523 +- 37.6289      6      bad       <--
chromium@418823                          971.935 +- 11.6164      6      bad
chromium@418824                          974.21 +- 29.9618       6      bad
chromium@418828                          979.513 +- 27.2047      6      bad
chromium@418844                          967.913 +- 82.9599      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.html5rocks.com.en. page_cycler_v2.typical_25

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

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


| 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!