Closed Bug 1266556 Opened 9 years ago Closed 8 years ago

Intermittent test_dataChannel_basicAudio.html | PeerConnectionWrapper (pcRemote): legal ICE state transition from new to failed

Categories

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

Product:
Core
Component:
WebRTC: Networking
Version:
48 Branch
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox48 --- affected

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure)

Is this a dup of any we have already?
Rank: 35
Component: Audio/Video → WebRTC: Networking
Flags: needinfo?(drno)
Priority: -- → P3
Well it's a generic ICE timeout on Android. And without timing information in the log and without any further useful log files we can't tell in which part things got slowed down so much that it caused the failure.... Maybe we should create some meta bugs for ICE timeouts and link intermittents to that/these meta bug(s) to be able to tell how much of a problem we have with ICE timeouts on treeherder (I don't think something like that exists).
Flags: needinfo?(drno)
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.