Closed
Bug 1503351
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 13788 - Add RTCPeerConnection.connectionState and onconnectionstate.
Categories
(Core :: WebRTC, enhancement, P4)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 13788 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/13788
Details from upstream follow.
Jonas Olsson <jonasolsson@chromium.org> wrote:
> Add RTCPeerConnection.connectionState and onconnectionstate.
>
> Bug: chromium:823144
> Change-Id: Ia849f44d1c8898da0fcb8341c8ff56de4de2d815
> Reviewed-on: https://chromium-review.googlesource.com/1292560
> WPT-Export-Revision: 38671ed5a409573c6a0cdaa71876918b714c7fd3
| Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → WebRTC
Product: Testing → Core
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=2eafa03b871b3b45af5716e27a00c01bc00b4670
| Assignee | ||
Comment 3•7 years ago
|
||
| Assignee | ||
Comment 4•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=07024c63b8c46eba73e5921db92b2991cdcf0044
| Assignee | ||
Comment 5•7 years ago
|
||
| Assignee | ||
Comment 6•7 years ago
|
||
| Assignee | ||
Comment 7•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=40822f100332f78e7eb94581354051f0befdc5fe
| Assignee | ||
Comment 8•7 years ago
|
||
| Assignee | ||
Comment 9•7 years ago
|
||
Ran 1 tests and 4 subtests
FAIL : 2
TIMEOUT: 3
Existing tests that now have a worse result (e.g. they used to PASS and now FAIL):
/webrtc/RTCPeerConnection-connectionState.html: TIMEOUT
connection with one data channel should eventually have connected connection state: TIMEOUT
New tests that have failures or other problems:
/webrtc/RTCPeerConnection-connectionState.html
Closing the connection should set connectionState to closed: FAIL
connection with one data channel should eventually have transports in connected state: TIMEOUT
| Assignee | ||
Comment 10•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=9d356cad4addbcf74c337b88094574528e97ce08
Comment 11•7 years ago
|
||
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9b073aa19f6a
[wpt PR 13788] - Add RTCPeerConnection.connectionState and onconnectionstatechange., a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/5f1fcc55c350
[wpt PR 13788] - Update wpt metadata, a=testonly
Comment 12•7 years ago
|
||
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8ac038131792
[wpt PR 13788] - Add RTCPeerConnection.connectionState and onconnectionstatechange., a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/f84858e99a2e
[wpt PR 13788] - Update wpt metadata, a=testonly
Comment 13•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8ac038131792
https://hg.mozilla.org/mozilla-central/rev/f84858e99a2e
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in
before you can comment on or make changes to this bug.
Description
•