Closed Bug 1207384 Opened 10 years ago Closed 6 years ago

Intermittent test_peerConnection_closeDuringIce.html | Test timed out.

Categories

(Core :: WebRTC: Networking, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure)

Looks like we never reached the checking state, even though the ICE candidates were successfully added (according to return values in JS land). Byron do we have a timer between sRD and adding ICE candidates (that the time is too long as we are on the famous B2G emu here again)?
Flags: needinfo?(docfaraday)
Any delay between setRemoteDescription and addIceCandidate would be from the mochitest, and looking at the logging there does not appear to be a delay like that. From what I can tell, the ICE stack never even starts gathering. This could be because STS isn't getting cycles, or it could be that the proxy lookup is never completing, since that needs to happen before gathering starts.
Flags: needinfo?(docfaraday)
backlog: --- → webrtc/webaudio+
Rank: 45
Priority: -- → P4
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.