8d65e9ab98
BandwidthEndToEndTest failed when I tested it with the new task-queue based paced sender. This turned out to be issues with this test. Problems fixed by this CL: 1. Send-side BWE not set up correctly. Caused probing to fail. 2. Test waited for non-zero pacer delay, but the new pacer will not generate any delay in this scenario. 3. Race condition during shutdown of test. 1) Is just a matter of configiuring the right header extension. 2) Set up test with high encoder bitrate to trigger pacer delay. 3) TaskQueue outlives the Call instances used in test, so make sure they are not referenced from lambda during teardown. Bug: webrtc:10809 Change-Id: I6393975691dfa05eb5b25d9283e476062e23a876 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158722 Reviewed-by: Sebastian Jansson <srte@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29669}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct