On 3/12/15 6:51 PM, Jonathan Griffin wrote:
What other use cases would you like us to address, which aren't derivatives
of the above issues?
I ran into a problem just yesterday: I wanted to run mochitest-browser
locally, to debug an error that happened very early in the test run startup.
So I did:
mach mochitest-browser --debugger=gdb
and hit my breakpoint and so forth... then quit the debugger.
Then the test harness respawned another debugger to run more tests. And
then another.
When run outside the debugger, I couldn't get the test harness to stop
at all (e.g. via hitting Ctrl-C a bunch of times).
The only way I found to stop it was to kill the mach process itself.
That left ssltunnel and various other processes still hanging out that
had to be killed one by one so I could try running the tests again.
Having some reliable way to kill a mochitest-browser run would be really
helpful.
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
