Use propagated clock in RtcEventLog unittests * Provide clock to EventGenerator and use it thus no longer rely on RtcEvent constructor to populate the timestamp. * Relax expectation of the log time to be within 1 ms instead of that it rounds to ms in a specific way. * For all log times (except utc time) use non-global SimulcatedClock instead of global FakeClock * Providing clock to the RtcEventLog implementation through Environment, * while at it, switch to CreateTestEnvironment. In particular that helper has simpler api for providing field trials keeping the same test functionality Bug: webrtc:42223992 Change-Id: I1c8184143b1ef1736c66af526c88065a26f36b77 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/419540 Reviewed-by: Björn Terelius <terelius@webrtc.org> Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/main@{#46018}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.