| commit | ec19d5ea79ca5b4222d702030f8fd042604cc08a | [log] [tgz] |
|---|---|---|
| author | Victor Boivie <boivie@webrtc.org> | Thu Oct 28 12:45:20 2021 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 28 15:01:40 2021 |
| tree | 348f905bc14dfdfbe737b18ad80fba180a2b07d4 | |
| parent | d891c4940a2a9e3cf1a644b0e73acf311f8ebc05 [diff] |
dcsctp: Don't run network tests with TSAN or MSAN Networks tests were previously disabled if building in debug mode as debug mode adds DCHECKs, and when DCHECKs are enabled, a lot of the components in dcSCTP will add consistency checks, and they can be really expensive to run in these network tests. However, if running in with TSAN or MSAN sanitizers and with DCHECKs enabled, they also take a long time. Current run-time on my relatively fast CPU (with is_debug=false): (no sanitizer) always_dcheck=false: 2.5s (no sanitizer) always_dcheck=true: 31s is_tsan=true, always_dcheck=false: 53s is_tsan=true, always_dcheck=true: 5m50s <-- too slow is_asan=true, always_dcheck=false: 13s is_asan=true, always_dcheck=true: 47s is_msan=true, always_dcheck=false: 35s is_msan=true, always_dcheck=true: 1m53s <-- too slow Note that buildbots may be much slower than my computer. Bug: webrtc:12943 Change-Id: If044ee9936372d54c9899b4864156c9f680af0b6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/236581 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35276}
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.