commit | 5ae3a028c862bd97a7b52c3d798f5f06a4f65214 | [log] [tgz] |
---|---|---|
author | Danil Chapovalov <danilchap@webrtc.org> | Mon Nov 12 11:29:27 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Nov 12 12:30:06 2018 +0000 |
tree | de5a536a1b004e55764607200fc22d73132998d2 | |
parent | 20f60f0dc61998244ab38834f48f0319adaacec2 [diff] |
Revert "Run robolectric tests for Android on several Android API versions" This reverts commit e598e6bff9528f77dc9f4fb3a5954ec5fb6790b0. Reason for revert: Main suspect of increased Android tests flakiness Original change's description: > Run robolectric tests for Android on several Android API versions > > Depends on https://bugs.chromium.org/p/chromium/issues/detail?id=901324 > > Bug: webrtc:9955 > Change-Id: I5e3f4c05b8258b90728644846f425ee131fda8d4 > Reviewed-on: https://webrtc-review.googlesource.com/c/109160 > Reviewed-by: Artem Titarenko <artit@webrtc.org> > Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> > Reviewed-by: Patrik Höglund <phoglund@webrtc.org> > Commit-Queue: Artem Titarenko <artit@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#25582} TBR=phoglund@webrtc.org,magjed@webrtc.org,sakal@webrtc.org,artit@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:9955 Change-Id: I62c4c9c3238f777b6017701bc1332d8661308f9c Reviewed-on: https://webrtc-review.googlesource.com/c/110609 Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25595}
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.