commit | 5d8f8fa0b6816bf3bd0f09e60110dc515403a109 | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Fri Apr 13 15:22:50 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Apr 13 16:22:38 2018 |
tree | e697ef0570ae25f09645a9bd7e5ac436e77e2926 | |
parent | fafeac3517a8c2c702bf3f65dfe4ac0493eb5874 [diff] |
Revert "Adding test for adding ICE candidate before applying answer." This reverts commit dd59d7049158a25f97ab1c7d381bfb4f8ed127c7. Reason for revert: Speculatively reverting this due to chromium test. The AutoRoller has been turned off for a couple of days due to the M67 branch cut. Did this cause a regression that made it into M67 or are the tests broken? Failed roll: https://chromium-review.googlesource.com/c/chromium/src/+/1011676 Example run: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_rel_ng/24406 Expected diff: https://isolateserver.appspot.com/browse?namespace=default-gzip&digest=77d652517595443eea13f6ba9aaff67728305213&as=RTCPeerConnection-addIceCandidate-diff.txt Original change's description: > Adding test for adding ICE candidate before applying answer. > > This was working before, but somewhat by accident (because an error > wasn't being surfaced). > > This CL also starts surfacing that error, from > JsepTransportController::AddRemoteCandidates to PeerConnection. > > Bug: None > Change-Id: Ib48c9c00ea2a5baa5f7e3210c5dc7a339498b2d0 > Reviewed-on: https://webrtc-review.googlesource.com/69015 > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#22830} TBR=steveanton@webrtc.org,deadbeef@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: None Change-Id: I78a1df5d1e38569d02565bf343881420cc171347 Reviewed-on: https://webrtc-review.googlesource.com/69860 Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22863}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.