There's some problem which is causing the Marionette actor not to get connected to the debugger. Attempting to send any Marionette message results in: response {u'message': u'Actor "conn4.1" does not recognize the packet type "getMarionetteID"', u'from': u'root', u'error': u'unrecognizedPacketType'} There have been no recent changes to Marionette or the debugger that would explain this. In addition, we only see this error on tests running on unagis and pandas.

caused by: https://github.com/mozilla-b2g/gaia/commit/a86c204de00a83fede1c1ff7b4169da72c489af5

I'm going to propose that if MARIONETTE is enabled, then adb will be always enabled, and disconnected from the remote-debugger setting. The crux of the problem is that marionette wants adb on, but the remote debugger off. What this means is that the remote debugger will always default to being off (so more or less reversing the gaia change mentioned in comment 1). For non-user builds adb will always be on. For user builds adb will be coupled to the remote debugger setting.

Nominating for tef? since this blocks bug 836621. Our partners run marionette tests, so they'll need/want this.

We do automated testing on -userdebug fyi.

This forces adb to be on when marionette is enabled (marionette requires that the remote-debugger be disabled).

Blocks another tef+ blocker.

https://hg.mozilla.org/releases/mozilla-b2g18/rev/c6ef8bcf0b8d https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_0/rev/b21f703f1db1

dev-doc-needed is to document the fact that adb is always on for non-user builds (i.e. eng and userdebug) and for user (i.e. production/dogfooding) builds adb is controlled via the remote- debugger setting.

Verified FIXED; our builds are back and running fine with the fix, thanks!