Triage new failures in RTCPeerConnection-iceConnectionState.https.html, RTCPeerConnection-onicecandidateerror.html, and protocol/candidate-exchange.https.html
Categories
(Core :: WebRTC: Signaling, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
Details
Attachments
(1 file)
Latest merge from upstream added some expected failures in these test cases. Need to figure out why, file new bugs if necessary, and put bug numbers in the .ini files.
[RTCPeerConnection-iceConnectionState.https.html]
[connection with one data channel should eventually have connected connection state]
bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1278299
expected: FAIL
[iceConnectionState changes at the right time, with bundle policy max-bundle]
expected: FAIL
[iceConnectionState changes at the right time, with bundle policy max-compat]
expected: FAIL
[iceConnectionState changes at the right time, with bundle policy balanced]
expected: FAIL
[RTCPeerConnection-onicecandidateerror.html]
expected: TIMEOUT
[Surfacing onicecandidateerror]
expected: TIMEOUT
[candidate-exchange.https.html]
[Adding only caller -> callee candidates gives a connection]
expected: FAIL
[Adding only callee -> caller candidates gives a connection]
expected: FAIL
[Explicit offer/answer exchange gives a connection]
expected: FAIL
[Adding callee -> caller candidates from end-of-candidates gives a connection]
expected: FAIL
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=9faacc68fab8e33289f43cc8b36a66186a9078aa
Pushed by bcampen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/442717bb5f48 Put bug links in these .ini files. r=jib
Comment 4•5 years ago
|
||
bugherder |
Description
•