Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Revert "WPT tests for setRemoteDescription for adding and rem…
…oving tracks."" This reverts commit 4e8a1ff7c4f07b2154a40f9ff50b418ecf6df0a9. Reason for revert: The original CL was reverted because the eventSequence keeping track of the order of ontrack firing and setRemoteDescription resolving was not modified when ontrack fired, rather upon a promise resolving that was resolved when ontrack fires. This added a delay and the order of promise then() callbacks became indeterminate. In this reland, ontrack has been modified to do eventSequence += 'ontrack;' instead. The original CL was reverted because of expecting: FAIL ontrack fires before setRemoteDescription resolves. assert_equals: expected "ontrack;setRemoteDescription;" but got "setRemoteDescription;ontrack;" But got: PASS ontrack fires before setRemoteDescription resolves. Original change's description: > Revert "WPT tests for setRemoteDescription for adding and removing tracks." > > This reverts commit 7224091bcdc52f1d9c7f6a8eecb3e7414f29aaeb. > > Reason for revert: causes tests failures on mac, e.g. https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests/builds/19421 > > May or may not be related to an unrelated revert that followed this original patch, https://chromium-review.googlesource.com/729719 > > Original change's description: > > WPT tests for setRemoteDescription for adding and removing tracks. > > > > These are behavior-driven tests, each test testing a specific behavior: > > - addTrack() with a track and no stream should fire ontrack with a > > remote track with the same ID and no streams. > > - addTrack() with a track and a stream should fire ontrack with a > > remote track and stream with matching IDs. > > - addTrack() with two tracks and a shared stream should fire ontrack > > twice with remote tracks and a shared remote stream, with matching > > IDs. > > - addTrack() with a track and two streams should fire ontrack with a > > track and two streams with matching IDs. > > - ontrack should fire before setRemoteDescription()'s promise resolves. > > - ontrack's receiver should match getReceivers(). > > - removeTrack() should not result in a receiver being removed. > > > > Unlike RTCPeerConnection-ontrack.https.html, these tests do not rely on > > transceiver support. When testing a behavior like "fires an event with > > a track" the test does not test unrelated things like the event being a > > complete implementation of RTCTrackEvent with transceivers and all. > > > > In a follow-up, I will add tests for other behavior associated with the > > removal of a track, including onmute events firing and the track being > > removed from the remote streams. > > > > Bug: 774303 > > Change-Id: I87d8a79d9e2e385610f749a9146b740cc649cf3f > > Reviewed-on: https://chromium-review.googlesource.com/719615 > > Commit-Queue: Henrik Boström <[email protected]> > > Reviewed-by: Taylor Brandstetter <[email protected]> > > Reviewed-by: Philip Jägenstedt <[email protected]> > > Cr-Commit-Position: refs/heads/master@{#510241} > > [email protected],[email protected],[email protected] > > Change-Id: I8684d63e478a2ce63d760d9ec2a973b27f985729 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 774303 > Reviewed-on: https://chromium-review.googlesource.com/730723 > Reviewed-by: Mikel Astiz <[email protected]> > Commit-Queue: Mikel Astiz <[email protected]> > Cr-Commit-Position: refs/heads/master@{#510404} [email protected],[email protected],[email protected],[email protected] Change-Id: I5f18c4426b9e39afbdf59537ad084c4ae461b54a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 774303 Reviewed-on: https://chromium-review.googlesource.com/731245 Reviewed-by: Henrik Boström <[email protected]> Commit-Queue: Henrik Boström <[email protected]> Cr-Commit-Position: refs/heads/master@{#510858}
- Loading branch information