commit | 2f042f26a3d0c062c43dc553058a286bd4dd8f19 | [log] [tgz] |
---|---|---|
author | kjellander <kjellander@webrtc.org> | Sun Dec 20 12:25:12 2015 -0800 |
committer | Commit bot <commit-bot@chromium.org> | Sun Dec 20 20:25:17 2015 +0000 |
tree | dba697bf2cf9d9c3bf34f592657569082d0d98f8 | |
parent | a4df27b6713583045e51e20c4eb93718d15ca33e [diff] |
Roll chromium_revision 1b6c421..db567a8 (365999:366304) I had to disable some Dtls12Both tests failing under MSan (see bug). Notice those errors started happening in the range of https://boringssl.googlesource.com/boringssl.git/+log/afd565f..9f897b2 while this CL brings in an even newer BoringSSL (that still has the same problem). Change log: https://chromium.googlesource.com/chromium/src/+log/1b6c421..db567a8 Full diff: https://chromium.googlesource.com/chromium/src/+/1b6c421..db567a8 Changed dependencies: * src/third_party/boringssl/src: https://boringssl.googlesource.com/boringssl.git/+log/afd565f..afe57cb * src/third_party/libyuv: https://chromium.googlesource.com/libyuv/libyuv.git/+log/1019e45..1ccbf8f * src/third_party/nss: https://chromium.googlesource.com/chromium/deps/nss.git/+log/a676aa0..aee1b12 DEPS diff: https://chromium.googlesource.com/chromium/src/+/1b6c421..db567a8/DEPS No update to Clang. NOTRY=True BUG=webrtc:5381 TBR=torbjorng@webrtc.org, pthatcher@webrtc.org Review URL: https://codereview.webrtc.org/1533253002 Cr-Commit-Position: refs/heads/master@{#11095}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.