Re: Android SSH Tunneling

[John Chen]

Please see http://go/android-wfh for information on this.

On Wed, Jul 8, 2020 at 12:57 PM Jonathan Ross <jon...@google.com> wrote:

Hi,

I am looking to run some telemetry stories on a local Android device. I have a Linux desktop back at the office, however locally I do not have a Linux machine.

While working on a Macbook I have been able to use SSH Tunneling to forward Port 5037. Using this I can deploy builds done on the remote Linux machine to the Android connected to the local Macbook. Using:

         out/droid/bin/chrome_public_apk install

However I run into an error when attempting to run telemetry from the remote Linux machine:

vpython ./tools/perf/run_benchmark rendering.mobile --story=canvas_05000_pixels_per_second --browser=android-chrome

(CRITICAL) 2020-07-08 15:36:10,188 timeout_retry.Run:178  (TimeoutThread-1-for-MainThread) Exception on _RunAdbCmd(<class 'devil.android.sdk.adb_wrapper.AdbWrapper'>, ['devices'], retries=2, timeout=30), attempt 1 of 3: AdbCommandFailedError("adb devices: failed with exit status 1 and output:\n- cannot bind 'tcp:5037': Address already in use\n- ADB server didn't ACK\n- * failed to start daemon *\n- error: \n- error: \n- List of devices attached\n- adb server is out of date.  killing...\n",)

(CRITICAL) 2020-07-08 15:36:12,357 timeout_retry.Run:178  (TimeoutThread-2-for-MainThread) Exception on _RunAdbCmd(<class 'devil.android.sdk.adb_wrapper.AdbWrapper'>, ['devices'], retries=2, timeout=30), attempt 2 of 3: AdbCommandFailedError("adb devices: failed with exit status 1 and output:\n- cannot bind 'tcp:5037': Address already in use\n- ADB server didn't ACK\n- * failed to start daemon *\n- error: protocol fault (couldn't read status): Connection reset by peer\n- error: protocol fault (couldn't read status): Connection reset by peer\n- List of devices attached\n- adb server is out of date.  killing...\n",)

(CRITICAL) 2020-07-08 15:36:14,666 timeout_retry.Run:178  (TimeoutThread-1-for-MainThread) Exception on _RunAdbCmd(<class 'devil.android.sdk.adb_wrapper.AdbWrapper'>, ['kill-server'], retries=2, timeout=30), attempt 1 of 3: AdbCommandFailedError('adb kill-server: failed with exit status 1 and output:\n- * server not running *\n',)

(CRITICAL) 2020-07-08 15:36:14,768 timeout_retry.Run:178  (TimeoutThread-2-for-MainThread) Exception on _RunAdbCmd(<class 'devil.android.sdk.adb_wrapper.AdbWrapper'>, ['kill-server'], retries=2, timeout=30), attempt 2 of 3: AdbCommandFailedError('adb kill-server: failed with exit status 1 and output:\n- * server not running *\n',)

It seems that the run_benchmark attempts to bind the port which is already in use.

Has anyone seen something similar? I couldn't see any flag for using an existing port, nor a backend that just uses the pre-installed chrome_public_apk.

Any thoughts would be appreciated.

Regards,

Jonathan

[Liviu Tinta]

Hi,

I have the exact same problem. 

Jonathan, have you found a solution?

Regards,

Liviu