Closed Bug 853787 Opened 8 years ago Closed 8 years ago
Report errors in nested event loops in xpcshell tests
When an xpcshell test fails due to an error in a nested event loop (when the debuggee is paused), the test harness is not notified and just times out after a while. This is especially troublesome in our build infrastructure, because failing tests never output a useful log to figure out what happened. When running locally one can always send a SIGINT (Ctrl-C) after a while and stop the test while seeing the output log. We should either simulate that behavior in the test harness (SIGINT before SIGKILL), or have the XPCOM component collect the errors and resume execution to fail the test immediately.
This makes our test case work. If we exit any nested event loops when the test is about to fail, it finishes normally.
Assignee: nobody → past
Status: NEW → ASSIGNED
Attachment #733524 - Flags: review?(jimb)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 23
You need to log in before you can comment on or make changes to this bug.