| commit | 3c9bcc1f7ae19fdc758b7ab0d4b643e28a473118 | [log] [tgz] |
|---|---|---|
| author | Tommi <tommi@webrtc.org> | Wed Apr 15 14:45:47 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Apr 15 16:09:44 2020 |
| tree | ef54b398fc6278547b39e7ef8a5277d29e49d004 | |
| parent | 4a5bce96e8c21a9b5e626f5e33d329a5555332f7 [diff] |
Reland of the test portion of: https://webrtc-review.googlesource.com/c/src/+/172847 ------------ original description -------------- Preparation for ReceiveStatisticsProxy lock reduction. Update tests to call VideoReceiveStream::GetStats() in the same or at least similar way it gets called in production (construction thread, same TQ/thread). Mapped out threads and context for ReceiveStatisticsProxy, VideoQualityObserver and VideoReceiveStream. Added follow-up TODOs for webrtc:11489. One functional change in ReceiveStatisticsProxy is that when sender side RtcpPacketTypesCounterUpdated calls are made, the counter is updated asynchronously since the sender calls the method on a different thread than the receiver. Make CallClient::SendTask public to allow tests to run tasks in the right context. CallClient already does this internally for GetStats. Remove 10 sec sleep in StopSendingKeyframeRequestsForInactiveStream. Bug: webrtc:11489 Change-Id: I491e13344b9fa714de0741dd927d907de7e39e83 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/173583 Commit-Queue: Tommi <tommi@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31077}
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.