| commit | db758c2589a983a7dd94dfdd9272892e28251fe4 | [log] [tgz] |
|---|---|---|
| author | ehmaldonado <ehmaldonado@webrtc.org> | Thu Aug 17 13:07:02 2017 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Aug 17 13:07:02 2017 |
| tree | ce58af6a85e356fab6089e3c37ffb01e4a10f1c7 | |
| parent | a9732656221e0033ab93ecf01cf07f71817da1e8 [diff] |
Revert of Make it possible for tests to set up trace event handlers. (patchset #4 id:60001 of https://codereview.webrtc.org/3002663002/ ) Reason for revert: Breaks Chromium bots. https://build.chromium.org/p/chromium.webrtc.fyi/builders/Mac%20Builder/builds/27340/steps/generate_build_files/logs/stdio Original issue's description: > Make it possible for tests to set up trace event handlers. > > As it is now, the first time a TRACE_EVENT... is called, the result from > the current handler is stored in a static const variable, and subsequent > calls will use that value regardless of changes to the handler. > > This is a problem if a test wants to use another handler. > > BUG=None > > Review-Url: https://codereview.webrtc.org/3002663002 > Cr-Commit-Position: refs/heads/master@{#19382} > Committed: https://chromium.googlesource.com/external/webrtc/+/a9732656221e0033ab93ecf01cf07f71817da1e8 TBR=hbos@webrtc.org,kwiberg@webrtc.org,mbonadei@webrtc.org,kjellander@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=None Review-Url: https://codereview.webrtc.org/2997963002 Cr-Commit-Position: refs/heads/master@{#19383}
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.