| commit | e828a39a7209feda1f3ed9b98bff4ac3f461b694 | [log] [tgz] |
|---|---|---|
| author | Tomas Gunnarsson <tommi@webrtc.org> | Thu May 29 09:30:06 2025 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 29 10:21:43 2025 |
| tree | 3487b8b74fc267cbac1f7e3582d14bbae42491a8 | |
| parent | f05cbb2f6d56cf05fe6645d2b47494382f6e44ef [diff] |
Revert "Use RunLoop::Flush instead of Sleep" This reverts commit c2af9bfde87cb6662d2be7a581236c345e454c53. Reason for revert: The change hasn't reduced flakiness of the test. See e.g. https://chromium-swarm.appspot.com/task?id=71305f8037899511&o=true&w=true Bug: webrtc:0 Original change's description: > Use RunLoop::Flush instead of Sleep > > This hopefully addresses flakiness in ResolveAfterDeleteDoesNotReturn > (at least on Windows) > Example run: > https://ci.chromium.org/ui/p/webrtc/builders/ci/Win64%20ASan/15860/overview > > > Bug: webrtc:0 > Change-Id: I1090dba592c15d2764c523a371bdc41aadaa0526 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/393080 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Auto-Submit: Tomas Gunnarsson <tommi@webrtc.org> > Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#44723} Bug: webrtc:0 Change-Id: I6a65c35980a39d6a269a6bc982d8b641c2b0efbd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/394200 Auto-Submit: Tomas Gunnarsson <tommi@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#44792}
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.