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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgubvMqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguf3NuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-ZLVvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguYjWvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2Z6E-ggM


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

android-galaxy-s5
chromium-rel-win7-x64-dual
win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1009
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/8999800514203710960

 Issue 648602  has been merged into this issue.

=== Auto-CCing suspected CL author nednguyen@google.com ===

Hi nednguyen@google.com, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Revert of Revert "[telemetry] Wire TsProxy through telemetry's network stack." (patchset #1 id:1 of https://codereview.chromium.org/2267613002/ )
Author  : nednguyen
Commit description:
  
Reason for revert:
Webview now support --proxy-server flag (see attached bug)

Original issue's description:
> Revert "[telemetry] Wire TsProxy through telemetry's network stack."
>
> This reverts commit 9fcccf0b65703994c9541273f00a993806a95356.
>
> Revert "[Telemetry] Explictly initialize & clean up network_controller"
>
> This reverts commit 30ce231266c6fb6147bb6df7c56a7eb75c23fccf.
>
> Seems like webview currently does not support proxy server?
> (See attached chromium bug)
>
> BUG=chromium:639632
> BUG=catapult:#2584
>
> TBR=pmeenan@chromium.org
>
> Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/947506bacfb5047857a52033256635faebf38af2

TBR=nednguyen@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=chromium:639632

Review-Url: https://codereview.chromium.org/2342503002
Commit  : b86cfef4b9da4749ff51e0fc4432869f8209dc42
Date    : Wed Sep 14 00:48:51 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N  Good?
chromium@418454                      263.203  9.45878  5  good
chromium@418462                      267.727  7.45602  5  good
chromium@418462,catapult@7d108c71d8  256.499  8.06709  5  good
chromium@418462,catapult@b86cfef4b9  981.98   11.3023  5  bad    <--
chromium@418463                      991.157  10.6671  5  bad
chromium@418464                      995.233  13.8868  5  bad
chromium@418466                      990.805  14.5189  5  bad
chromium@418469                      1001.25  38.8282  5  bad
chromium@418483                      990.724  4.50201  5  bad
chromium@418512                      1013.34  38.6249  5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 648599

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.basic_oopif
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___www.ebay.com
Relative Change: 285.00%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1057
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999800514203710960


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

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

These will all be invalid as they are specific to Samsung S5s, which we do not trust to give us a signal and have subsequently removed from the waterfalls. If you think this regression is real, please re-open.

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