commit | 97e35ce05d4b7921acd2d523780e3e1d2d402867 | [log] [tgz] |
---|---|---|
author | Artem Titarenko <artit@webrtc.org> | Tue Oct 30 10:17:54 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Oct 30 12:26:48 2018 |
tree | 4f881ba4d3d505176bf019005dcb38510f6ecd15 | |
parent | 0eb7d3ff35c552d873c02add91844568a71f2d61 [diff] |
Revert "Disabled TestPacketBuffer.SeqNumWrapOneFrame test due to clang update" This reverts commit 03c592a1e9f9dbad02bfc9d1f55d8b8c5c499208. Reason for revert: Problem with clang should be solved now Original change's description: > Disabled TestPacketBuffer.SeqNumWrapOneFrame test due to clang update > > Until further investigation. > Clang update: chromium:880827 > > Bug: chromium:887464 > Change-Id: Id1fe85a013920e6ae8c6ac69efb0a0502b9dd6fe > Reviewed-on: https://webrtc-review.googlesource.com/101561 > Commit-Queue: Artem Titarenko <artit@webrtc.org> > Reviewed-by: Artem Titarenko <artit@webrtc.org> > Reviewed-by: Patrik Höglund <phoglund@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24795} TBR=phoglund@webrtc.org,artit@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:887464 Change-Id: Id4d1722b289d9f56ae2aebf576f28f3b02a4c942 Reviewed-on: https://webrtc-review.googlesource.com/c/108583 Reviewed-by: Artem Titarenko <artit@webrtc.org> Reviewed-by: Patrik Höglund <phoglund@webrtc.org> Commit-Queue: Artem Titarenko <artit@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25428}
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.