Panos Astithas (he/him) [:past] (please ni?) Assignee
	Description • 12 years ago

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.

	Panos Astithas (he/him) [:past] (please ni?) Assignee
	Comment 1 • 12 years ago

This makes our test case work. If we exit any nested event loops when the test is about to fail, it finishes normally.

	Panos Astithas (he/him) [:past] (please ni?) Assignee
	Comment 2 • 12 years ago

https://hg.mozilla.org/integration/fx-team/rev/c54b8b913a70

	Victor Porof [:vporof][:vp]
	Comment 3 • 12 years ago

https://hg.mozilla.org/mozilla-central/rev/c54b8b913a70