Fix get_chrome_remote_debugging_port |
|||
Issue descriptionget_chrome_remote_debugging_port: https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/bin/utils.py?l=1179-1188 This code reads the remote-debugging-port from chrome's command line. This can now be 0 as chrome picks an ephemeral port, and ought to be read from /home/chronos/DevToolsActivePort, as we do here: https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py?l=56-76
,
Aug 10 2017
,
Aug 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/e3adb0a2a7ca0977d1fc99b7ca02c25a1bca4193 commit e3adb0a2a7ca0977d1fc99b7ca02c25a1bca4193 Author: Achuith Bhandarkar <achuith@chromium.org> Date: Fri Aug 11 05:47:28 2017 autotest: Fix get_chrome_remote_debugging_port to handle ephemeral port. BUG= chromium:754433 TEST=security_NetworkListeners Change-Id: Ic748e4a0db2059943a21530e25f37d15848edb32 Reviewed-on: https://chromium-review.googlesource.com/611152 Commit-Ready: Achuith Bhandarkar <achuith@chromium.org> Tested-by: Achuith Bhandarkar <achuith@chromium.org> Reviewed-by: Achuith Bhandarkar <achuith@chromium.org> [modify] https://crrev.com/e3adb0a2a7ca0977d1fc99b7ca02c25a1bca4193/client/bin/utils.py
,
Aug 11 2017
,
Jan 22 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by achuith@chromium.org
, Aug 10 2017