| commit | dfe6937666886a005207b45015ea7b33c1c512b7 | [log] [tgz] |
|---|---|---|
| author | kjellander <kjellander@webrtc.org> | Mon Jun 13 14:11:02 2016 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Mon Jun 13 21:11:09 2016 +0000 |
| tree | e2d8a4eb8056f52499ef9f8f2cfa9f11326e00cc | |
| parent | c49cf1308f879ce029f5f0e804b4eef3b08b67c5 [diff] |
Revert of Roll chromium_revision 7fa6701bc5..1a73d11e65 (398458:399420) (patchset #2 id:20001 of https://codereview.webrtc.org/2061723002/ ) Reason for revert: webrtc_perf_tests fails on all Android Release testers: http://build.chromium.org/p/client.webrtc/builders/Android64%20Tests%20%28L%20Nexus9%29/builds/3673 Original issue's description: > Roll chromium_revision 7fa6701bc5..1a73d11e65 (398458:399420) > > A fix was needed to make Android tests pass after > https://codereview.chromium.org/2043803003 > > Change log: https://chromium.googlesource.com/chromium/src/+log/7fa6701bc5..1a73d11e65 > Full diff: https://chromium.googlesource.com/chromium/src/+/7fa6701bc5..1a73d11e65 > > Changed dependencies: > * src/buildtools: https://chromium.googlesource.com/chromium/buildtools.git/+log/8dd3c8e39a..099f1da55b > * src/third_party/boringssl/src: https://boringssl.googlesource.com/boringssl.git/+log/0fc7df55c0..171b5403ee > * src/third_party/ffmpeg: https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/7f03319b9d..bcb8b67b8b > DEPS diff: https://chromium.googlesource.com/chromium/src/+/7fa6701bc5..1a73d11e65/DEPS > > No update to Clang. > > TBR= > BUG=webrtc:5990 > NOTRY=True > > Committed: https://crrev.com/c49cf1308f879ce029f5f0e804b4eef3b08b67c5 > Cr-Commit-Position: refs/heads/master@{#13117} TBR= # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5990 Review-Url: https://codereview.webrtc.org/2059423002 Cr-Commit-Position: refs/heads/master@{#13118}
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.