Open Bug 987139 (asyncfailures) Opened 10 years ago Updated 2 years ago

[meta] Asynchronous/lazy errors should cause test failures


(Firefox :: General, defect)





(Reporter: Yoric, Unassigned)


(Depends on 2 open bugs)


(Keywords: meta)

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.
Summary: Asynchronous/lazy errors should cause test failures → [meta] Asynchronous/lazy errors should cause test 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.
Alias: asyncfailures
Depends on: 989960
No longer blocks: 976205
No longer depends on: 1019670
Depends on: 1242505
Keywords: meta
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.