Commit c995ccc1 authored by webrtc-chromium-autoroll's avatar webrtc-chromium-autoroll Committed by Commit Bot

Roll src/third_party/webrtc 5c71e74331bd..9f2e62402443 (2 commits)

https://webrtc.googlesource.com/src.git/+log/5c71e74331bd..9f2e62402443


git log 5c71e74331bd..9f2e62402443 --date=short --no-merges --format='%ad %ae %s'
2018-07-02 henrik.lundin@webrtc.org Break out NetEqEventLogInput to separate source files
2018-07-02 aleloi@webrtc.org Flags and settings for AGC2 in AgcManagerDirect.


Created with:
  gclient setdep -r src/third_party/webrtc@9f2e62402443

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I21452705d07dd365d790775b31bb98fa6c5d4b71
Reviewed-on: https://chromium-review.googlesource.com/1122896Reviewed-by: default avatarwebrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#571945}
parent 299c56ef
......@@ -1032,7 +1032,7 @@ deps = {
Var('chromium_git') + '/external/khronosgroup/webgl.git' + '@' + 'a5c263cc63ffc2cc189b5214074c8792067c1853',
'src/third_party/webrtc':
Var('webrtc_git') + '/src.git' + '@' + '5c71e74331bd57dd94be6d66d7490c1a95154e48',
Var('webrtc_git') + '/src.git' + '@' + '9f2e62402443acc8ffbb0dd0cd3e2e15461951e6',
'src/third_party/xdg-utils': {
'url': Var('chromium_git') + '/chromium/deps/xdg-utils.git' + '@' + 'd80274d5869b17b8c9067a1022e4416ee7ed5e0d',
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment