| commit | dec6108bdce9bc543674a7ef70db16c565e53b76 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Feb 17 17:57:59 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 17 17:57:59 2025 |
| tree | 4ac401f5a55ca69b19265010d9e8fde126102e7c | |
| parent | a344dd8167404889d567f253597a28e4460a471d [diff] |
Roll WebRTC from fa7c5b667443 to ff0256e8b63a (2 revisions) https://webrtc.googlesource.com/src.git/+log/fa7c5b667443..ff0256e8b63a 2025-02-17 phancke@meta.com Add unit test for "locking in" PTs offered by remote in subsequent O/A 2025-02-17 ssilkin@webrtc.org Delete WebRTC-LibaomAv1Encoder-AdaptiveMaxConsecDrops 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: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie215311038c2237ad93e85d06b0985f36f843814 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6276235 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1421111}
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.