with the newest jimdb (jim's gdb), you really don't need to press a button to continue. Instead, we can just rip out the press-a-button-to-continue debug intent, and just turn that into a Thread.sleep().
Created attachment 559927 [details] [diff] [review]
Comment on attachment 559927 [details] [diff] [review]
Seems ok to me
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/3950656acf1b - I'm pretty sure that you completely broke every test suite (by either failing to start up, or crashing, dunno which), though it's pretty funny that I was able to star all the failures right up until I realized that you were at 18 of 23 jobs all failed, and the bug 686091 failures were looking a little odd, because they were taking a bit more than 15 seconds.
Created attachment 564209 [details] [diff] [review]
Bug 686405 - remove the debug button and just wait 5s for the debugger
snorp - do we need the enum WaitForDebugger?
(In reply to Doug Turner (:dougt) from comment #6)
> snorp - do we need the enum WaitForDebugger?
Yeah, we're running the Android main loop for that 5s so I think it's a good idea to have a state for this.