Commit 2c41324f authored by chromium-autoroll's avatar chromium-autoroll Committed by Chromium LUCI CQ

Roll WebRTC from c463a784c340 to fec83cc86025 (3 revisions)

https://webrtc.googlesource.com/src.git/+log/c463a784c340..fec83cc86025

2020-12-23 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 2eaf311e..cc240573 (839031:839139)
2020-12-23 philipel@webrtc.org Remove unused NTP time functions from RtpPacketReceived.
2020-12-23 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision ad7eaf17..2eaf311e (838850:839031)

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/+doc/master/autoroll/README.md

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I849974bd57cbd90c14f5881e131d04d07fab2415
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602502Reviewed-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@{#839187}
parent afbcbf55
......@@ -1514,7 +1514,7 @@ deps = {
Var('chromium_git') + '/external/github.com/gpuweb/cts.git' + '@' + '3c2fe3888658d82b47ca831d59a2e07579619c2d',
'src/third_party/webrtc':
Var('webrtc_git') + '/src.git' + '@' + 'c463a784c340874c75032da7602ec1fde43f75ed',
Var('webrtc_git') + '/src.git' + '@' + 'fec83cc8602580ce1c078f7cd4e7f4d2be4ac850',
'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