Enable TURN on the host when using WebRTC.

remoting/test/protocol_perftest.cc

Index: remoting/test/protocol_perftest.cc
diff --git a/remoting/test/protocol_perftest.cc b/remoting/test/protocol_perftest.cc
index 355a5af3ff0f83226169eb98850cffb555086048..a1e5298e206425a1953c225e3e5b05d37125f6f5 100644
--- a/remoting/test/protocol_perftest.cc
+++ b/remoting/test/protocol_perftest.cc
@@ -333,7 +333,7 @@ class ProtocolPerfTest
     // else.
     host_.reset(new ChromotingHost(
         &desktop_environment_factory_, std::move(session_manager),
-        transport_context, host_thread_.task_runner(),
+        transport_context, transport_context, host_thread_.task_runner(),

[garykac, 2016/03/15 00:13:16]

Shouldn't there be separate ice_ and _webrtc_ transport_contexts here?

And do we run separate ice and webrtc perf tests?

[Sergey Ulanov, 2016/03/15 20:17:31]

Reverted this. There is no reason to use a different transport_context for
webrtc protocol.
There is TotalLatencyWebrtc that measures WebRTC protocol perf.

         encode_thread_.task_runner()));
 
     base::FilePath certs_dir(net::GetTestCertsDirectory());