Android: start upstreaming some of our perf tests.

tools/chrome_remote_control/chrome_remote_control/adb_commands.py

Index: tools/chrome_remote_control/chrome_remote_control/adb_commands.py
diff --git a/tools/chrome_remote_control/chrome_remote_control/adb_commands.py b/tools/chrome_remote_control/chrome_remote_control/adb_commands.py
index d0a35286547725a0f01b0e436736ac2dccb2ed5f..41636f3aa2450fed0c0f0b33e0b675b686cf5aab 100644
--- a/tools/chrome_remote_control/chrome_remote_control/adb_commands.py
+++ b/tools/chrome_remote_control/chrome_remote_control/adb_commands.py
@@ -119,6 +119,7 @@ class AdbCommands(object):
   def IsRootEnabled(self):
     return self._adb.IsRootEnabled()
 
+
 def HasForwarder(adb, buildtype=None):
   if not buildtype:
     return (HasForwarder(adb, buildtype='Release') or
@@ -126,11 +127,12 @@ def HasForwarder(adb, buildtype=None):
   return (os.path.exists(os.path.join('out', buildtype, 'device_forwarder')) and
           os.path.exists(os.path.join('out', buildtype, 'host_forwarder')))
 
+
 class Forwarder(object):
   def __init__(self, adb, host_port):
     assert HasForwarder(adb)
 
-    port_pairs = [(host_port, host_port), ]
+    port_pairs = [(0, host_port), ]

[tonyg, 2012/10/22 17:21:28]

Are you sure this works? I wouldn't expect it to.

When web page replay runs (only if you have src-internal checked out),
--testing-fixed-http-port causes all http requests to go to a fixed port. If the
port on the device doesn't match that, I don't see how replaying would work.

[bulach, 2012/10/22 17:29:02]

that's a good point. it worked for me, but you convinced me it'd break other
cases.. I just reverted this file then.

     tool = valgrind_tools.BaseTool()
 
     self._host_port = host_port