We have too many uncaught asynchronous errors in the testsuite. I suspect that many of them hide actual problems, or make these problems harder to find. They should cause the test suite to fail.

Glad to see work on this. i wanted to file a bug about Promise.jsm/Task.jsm. How about console.error() from jsm land? We have devtools code that uses console.error() for reporting errors. I was thinking we might want to report such console.error messages as well.

Well, we could certainly check out how many tests would fail if console.error() causes failures.

I'm not able to evaluate the impact of turning console.error() into errors, I'm afraid. I guess we would need to check the result. That can be quick-tested by just prepending TEST-UNEXPECTED-FAIL in front of any console.error message.