a06f360d5b
If 10ms delayed report is scheduled at 1.9ms (truncated by TaskQueue clock to 1ms) it may run at 11.1ms (truncated to 11ms, i.e. first time it look like 10ms passed). But (test) clock with different time offset may see passed time as 9ms which result in a test failure for a wrong reason. Relaxing period expectation by 1ms should mitigate the issue Bug: webrtc:8945 Change-Id: I902d8af436fc74d4a3a0ad8ffdb5a6d3565adb7d Reviewed-on: https://webrtc-review.googlesource.com/58095 Commit-Queue: Niels Moller <nisse@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22361}
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