commit | 94d8ccec4cc3b0a0285662346382ec4628cd127a | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Fri Jan 26 22:44:21 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 26 22:44:30 2018 +0000 |
tree | 552d1bc589a89799bb2c22e06c77cb3c21531aca | |
parent | 4954a77cf81e6793245f52d485834acd3e6eab1c [diff] |
Revert "Parameterize PeerConnection signaling tests for Unified Plan" This reverts commit 65c0a60302202189c37af91fca6abf092f022b1c. Reason for revert: Breaking downstream test which was calling CreateAnswer in stable state. Will reland after fixing test. Original change's description: > Parameterize PeerConnection signaling tests for Unified Plan > > This also changes the behavior of CreateAnswer to fail unless > the signaling state is kHaveRemoteOffer or kHaveLocalPranswer, > as per the WebRTC specification. > > Bug: webrtc:8765 > Change-Id: I60ac67cd92b17fcbff964afc14d049481e816a28 > Reviewed-on: https://webrtc-review.googlesource.com/41042 > Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> > Commit-Queue: Steve Anton <steveanton@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#21779} TBR=steveanton@webrtc.org,deadbeef@webrtc.org,pthatcher@webrtc.org Change-Id: I90eacadb217353a7e098826563f5aeaaced52452 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:8765 Reviewed-on: https://webrtc-review.googlesource.com/44581 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21781}
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.