So I realized while I had a bunch of smaller bugs for the issues I ran into when porting the B2G automation to SUT Agent, I didn't have an actual tracking bug for it.
Created attachment 676827 [details] [diff] [review] bitrotted WIP Here is my initial WIP patch with tons of print statements and bit rot.
Off the top of my head, here are some of the things we use adb for that I'll need to replicate some other way: 1) adb forward -> can't remember if this was just needed for emulators or other things too 2) adb remount -> apparently this can be achieved by running 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p2 /system' as root 3) using adb to start b2g.sh and retrieve output -> we'll probably need to copy the fennec method of pulling down a file every couple of seconds or something similar
(In reply to Andrew Halberstadt [:ahal] from comment #2) > Off the top of my head, here are some of the things we use adb for that I'll > need to replicate some other way: > > 1) adb forward -> can't remember if this was just needed for emulators or > other things too We do need adb forward for the emulator (we'll have to stick with adb instead of SUT in general for emulator tests). It may be useful to preserve adb mode as well for people running tests locally. We shouldn't need it all in SUTAgent mode, theoretically. However, there's currently a bug which prevents Marionette from accepting connections from a non-local socket which will have to be fixed (bug 800138) before we can completely convert to SUTAgent.
I think we will need adb forward functionality.. Negatus currently requires ports 20700 and 20701 to be forwarded: https://github.com/mozilla/Negatus
No, Negatus does not require adb; it's just a convenience, particularly for development, so that we can have a single script to build and install Negatus without having to know what the remote device's IP is. Negatus should have ports 20701 and 20700 open on whatever device it's running on.
Would this bug be needed to actually run tests on the pandas? Should this block bug 802317?
No this only blocks mochitests and reftests.
Unassigning myself as this is likely deferred to Q2
B2GAutomation is soon a thing of the past. A newer incarnation of this bug might be "Create a mozrunner capable of working with sutagent"