Commit 07b25655 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/webrtc bfe3ef8feb3b..261f792f836a (2 commits)

https://webrtc.googlesource.com/src.git/+log/bfe3ef8feb3b..261f792f836a

git log bfe3ef8feb3b..261f792f836a --date=short --first-parent --format='%ad %ae %s'
2020-01-31 sprang@webrtc.org Allow software fallback on lowest simulcast stream for temporal support
2020-01-31 phoglund@webrtc.org Implement histogram perf results writer.

Created with:
  gclient setdep -r src/third_party/webrtc@261f792f836a

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: chromium:1029452
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I9de66edbbb0ccd2bb8dce65d4834e578d00b56dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033412Reviewed-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@{#737425}
parent 1709c452
......@@ -1494,7 +1494,7 @@ deps = {
Var('chromium_git') + '/external/github.com/gpuweb/cts.git' + '@' + 'ec18cc3262922e7dcdbe70243c6f40606f979144',
'src/third_party/webrtc':
Var('webrtc_git') + '/src.git' + '@' + 'bfe3ef8feb3b4e351403be38fe626df4e796648c',
Var('webrtc_git') + '/src.git' + '@' + '261f792f836a26fc62cb5835635883a762134338',
'src/third_party/libgifcodec':
Var('skia_git') + '/libgifcodec' + '@'+ Var('libgifcodec_revision'),
......
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