de3f844a20
ClockTest.NtpTime was checking that the two methods for getting the system time are returning a value that is within a fixed error margin (100 ms) of each other. Unfortunately, even such a wide margin was sometimes exceeded on heavily loaded machines (https://build.chromium.org/p/client.webrtc/builders/Mac%20Asan/builds/9235/steps/system_wrappers_unittests/logs/stdio). This CL changes the test to sandwich clock->CurrentNtp() between clock->CurrentNtpTimeInMilliseconds(). This way the test will pass no matter how much time elapses between the two method calls, as long as the clock is monotonic. Repeated test runs showed that there may be 1 ms worth of rounding error between the two methods of getting time, so we have to allow that. BUG=None. Review-Url: https://codereview.webrtc.org/2393063002 Cr-Commit-Position: refs/heads/master@{#14520}
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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