:jesup has been having trouble for the last couple of days running 'mach test <some-mochitest.js>', on device or emulator, from a linux host. It appeared that android_device.py was hanging on one of its first adb commands. He reports he normally uses a tcsh shell, and everything started working fine for him when he switched to a bash shell. I don't immediately understand how our adb command handling would be influenced by the host shell. Command line escapes? He was using devicemanagerADB. Will ADBAndroid work better? Worse?

With current a mozilla-central build (using ADBAndroid), I tried running 'mach test <some-mochitest.js>' against the emulator, on Ubuntu 16.04, in tcsh -- it worked fine. I repeated with 'mach test <some-mochitest-dir>' - okay. Also checked robocop, xpcshell-test, 'mach install' and 'mach android-emulator' - all okay. Repeated all tests with bash, sh, csh, ksh - all okay. While not an exhaustive test, I think it's fair to say this works for me. Hopefully this was a problem with devicemanager and is now fixed.