9e74e57b8f
The test was assuming that after all thee layers have bytesSent > 0 we would have fully ramped up to the expected resolutions. But there are reasons why this may not be true, such as if adaptation kicks in. This CL attempts to de-flake by using kLongTimeoutForRampUp when checking the resolutions as well. // Just increasing a timeout... NOTRY=True Bug: webrtc:14884 Change-Id: I5ef57ec3e3cc99552c9ae32a6fdf07889ff06ee1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/296883 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39534}
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 here 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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation