When Raptor supports Marionette, we need to support connecting to remote devices, as that is how bitbar devices are set up. Specifically: MARIONETTE_HOST and MARIONETTE_PORT are provided in the environment. Handle forwarding adb when device is connected to localhost.
Created attachment 8635495 [details] [review] Link to Github pull-request: https://github.com/eliperelman/mozilla-raptor/pull/4
Created attachment 8635592 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/raptor/pull/5
Cmd line options work, but env vars don't: https://gist.github.com/rwood-moz/6eb2ff0aecff0450b6ef
Comment on attachment 8635592 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/raptor/pull/5 LGTM and works great with latest update. Didn't test with remote bitbar device, just tested locally, cmd line and env vars, multiple devices attached. ADB is now fw automatically by default, to the ANDROID_SERIAL device. Ran coldlaunch, restart, and reboot test, adb connection is retained through multiple reboot runs too.
Attachment #8635592 - Flags: review?(rwood) → review+
In master: https://github.com/mozilla-b2g/raptor/commit/7b3bd98f9bf58bbfcf6a0a50d804c0d1ae37b3ef In npm: @mozilla/raptor v1.2.0
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.