commit | 8909a63aca87e3426a48ab2c3e7369a64a4ad144 | [log] [tgz] |
---|---|---|
author | Niels Möller <nisse@webrtc.org> | Thu Sep 06 08:42:44 2018 +0200 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Sep 06 08:38:18 2018 +0000 |
tree | 06b539bbfcacdca17f185868f393450a1d5ecb55 | |
parent | bb081a62dc30a49fa77cfdbb4ae470c5137fa547 [diff] |
Reland "Explicitly wrap main thread in test_main.cc." This is a reland of 711a31aead9007e42dd73c302c8ec40f9e931619 Changes since original landing: Rename methods only used by tests, mainly via FakeClock, MessageQueueManager::ProcessAllMessageQueues --> ProcessAllMessageQueuesForTesting MessageQueue::IsProcessingMessages --> IsProcessingMessagesForTesting Fix the handling of null rtc::Thread::Current() in ProcessAllMessageQueuesInternal(). Add override Thread::IsProcessingMessagesForTesting() to return false for the wrapped main thread, unless it's also the current thread. In tests, the main thread is typically not processing any messages, but blocked in an Event::Wait(). Original change's description: > Explicitly wrap main thread in test_main.cc. > > Bug: webrtc:9714 > Change-Id: I6ee234f9a0b88b3656a683f2455c3e4b2acf0d54 > Reviewed-on: https://webrtc-review.googlesource.com/97683 > Reviewed-by: Tommi <tommi@webrtc.org> > Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> > Commit-Queue: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24560} Bug: webrtc:9714 Change-Id: I6f022d46aaf1e28f86f09f2d68c1803b69770126 Reviewed-on: https://webrtc-review.googlesource.com/98060 Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24596}
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 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.