| commit | ee2388f3f098dc0d153956a4ab95d1b60890f8c7 | [log] [tgz] |
|---|---|---|
| author | Guido Urdaneta <guidou@webrtc.org> | Thu Feb 15 16:36:19 2018 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 15 16:37:26 2018 |
| tree | 7de70b5c7b38a6c4d1e5e480512dec62dddde230 | |
| parent | 02fddf64a9de36d8a4d194a97a0bd8d40c4daaa8 [diff] |
Revert "Update RTCStatsCollector to work with RtpTransceivers" This reverts commit 56bae8ded39c3fab2635b7d2d1d17a87d5d2818b. Reason for revert: Speculative revert. This CL is suspect of making Chrome trybots fail the following test, preventing rolls: external/wpt/webrtc/RTCPeerConnection-track-stats.https.html Some failed roll attempts: https://chromium-review.googlesource.com/c/chromium/src/+/921421 https://chromium-review.googlesource.com/c/chromium/src/+/921422 https://chromium-review.googlesource.com/c/chromium/src/+/921781 Some failed bot runs: https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/647669 https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/103786 Original change's description: > Update RTCStatsCollector to work with RtpTransceivers > > Bug: webrtc:8764 > Change-Id: I8b442345869eb6d8b65fd12241ed7cb6e7d7ce3d > Reviewed-on: https://webrtc-review.googlesource.com/49580 > Commit-Queue: Steve Anton <steveanton@webrtc.org> > Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#22026} TBR=steveanton@webrtc.org,deadbeef@webrtc.org,hbos@webrtc.org,pthatcher@webrtc.org Change-Id: I21ce2109087d7b2d9470471ee9a6757f904296d2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:8764 Reviewed-on: https://webrtc-review.googlesource.com/54000 Reviewed-by: Guido Urdaneta <guidou@webrtc.org> Commit-Queue: Guido Urdaneta <guidou@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22036}
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.