Closed Bug 1479539 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 12237 - Fix RTCPeerConnection-transceivers.https.html bug.

Categories

(Core :: WebRTC, enhancement, P4)

Product:
Core
Component:
WebRTC
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12237 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12237 Details from upstream follow. Henrik Boström <hbos@chromium.org> wrote: > Fix RTCPeerConnection-transceivers.https.html bug. > > This PR accidentally made the "addTrack(0 streams)" test call addTrack() > with a stream, which broke the tests: > https://github.com/web-platform-tests/wpt/pull/12141 > > Test restored and all "addTrack/addTransceiver(X streams)" are made to > consistently use "new MediaStream()" the same way. > > Bug: 869036 > Change-Id: Ieaf0c73a1996aeb2e87e18f2f9065fa1e6fee1e7 > > Reviewed-on: https://chromium-review.googlesource.com/1155125 > WPT-Export-Revision: 0da9d6f9b29177e1a9a8b3d8dbb1554c84f0a647
PR 12237 applied with additional changes from upstream: ed8099ac2129f3f7a0f9f3a5e30e3b581d54cdee
Component: web-platform-tests → WebRTC
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 41 subtests OK : 1 PASS : 35 FAIL : 6
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e5221e193074 [wpt PR 12237] - Fix RTCPeerConnection-transceivers.https.html bug., a=testonly
https://hg.mozilla.org/mozilla-central/rev/e5221e193074
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.