commit | 86dfac112a9fad3fc46ec6f15ac5d4f1edf25100 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Jan 13 19:40:31 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 13 19:40:31 2025 |
tree | 72e270e268f65d427830c4d49d8049db17ed79b5 | |
parent | ddcf18f3b053a6904eb7419fb1e91f515a0c242c [diff] |
Roll WebRTC from 83861d5649c8 to da8a535ad4e4 (2 revisions) https://webrtc.googlesource.com/src.git/+log/83861d5649c8..da8a535ad4e4 2025-01-13 phancke@meta.com Fix RTX/sCP behavior 2025-01-13 danilchap@webrtc.org Propagate field trials into AgcManagerDirect 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,webrtc-infra@google.com on the revert to ensure that a human is aware of the problem. To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/issues/entry To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: chromium:387077342 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ib6cebe3bb425678d70b6599ecfe127272988011e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173076 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1405644}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.