Closed Bug 824923 Opened 7 years ago Closed 7 years ago

Stablize WebRTC mochitests against Javascript exceptions to prevent timeouts

Categories

(Core :: WebRTC, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla20

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

(Whiteboard: [WebRTC][blocking-webrtc+][qa-])

Attachments

(1 file)

We do not catch global JS exceptions within the WebRTC mochitests so far. That causes an early abort without the call of 'SimpleTest.finish()'. That means the test harness doesn't detect that the test has actually been finished. After 330s we kill the browser.

That should not happen and we have to improve our code by catching those global exceptions and to react accordingly.

The upcoming patch here will unhide the problem seen by bug 823056.
Attached patch Patch v1Splinter Review
Attachment #695988 - Flags: review?(rjesup)
Priority: -- → P2
Whiteboard: [WebRTC][automation-blocked][blocking-webrtc+]
Attachment #695988 - Flags: review?(rjesup) → review+
Blocks: 823056
https://hg.mozilla.org/mozilla-central/rev/e0d93141fe0c
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Flags: in-testsuite+
Whiteboard: [WebRTC][automation-blocked][blocking-webrtc+] → [WebRTC][automation-blocked][blocking-webrtc+][qa-]
Whiteboard: [WebRTC][automation-blocked][blocking-webrtc+][qa-] → [WebRTC][blocking-webrtc+][qa-]
You need to log in before you can comment on or make changes to this bug.