Commit c58c1b63 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/webrtc 895ce82cabc8..73d117f64ebb (3 commits)

https://webrtc.googlesource.com/src.git/+log/895ce82cabc8..73d117f64ebb


git log 895ce82cabc8..73d117f64ebb --date=short --no-merges --format='%ad %ae %s'
2018-10-02 brandtr@webrtc.org Split WebRTC-UseShortVP8TL3Pattern field trial in two.
2018-10-02 philipp.hancke@googlemail.com getStats: add relayProtocol
2018-10-02 aleloi@webrtc.org Reduce digital adaptive AGC2 gain in some situations.


Created with:
  gclient setdep -r src/third_party/webrtc@73d117f64ebb

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

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;luci.chromium.try:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Ifd5ada35335256725d83210eb85a0032af7ff85f
Reviewed-on: https://chromium-review.googlesource.com/1256236Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#595823}
parent 24d8c445
......@@ -1106,7 +1106,7 @@ deps = {
Var('chromium_git') + '/external/khronosgroup/webgl.git' + '@' + '6d2f3f4cb8bac1f7c4a945c73d07a33df74f22f9',
'src/third_party/webrtc':
Var('webrtc_git') + '/src.git' + '@' + '895ce82cabc83bc72bb5ee97b750b2d235901c17',
Var('webrtc_git') + '/src.git' + '@' + '73d117f64ebbfdc5d98c41014cd1782b533c7b98',
'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