Roll WebRTC from 9d96efa66362 to b089e05db91a (5 revisions) https://webrtc.googlesource.com/src.git/+log/9d96efa66362..b089e05db91a 2025-09-18 jsca@google.com Add update mechanism information to fft/README.chromium. 2025-09-18 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 6fe41a4828..1da737b59f (1517419:1517520) 2025-09-18 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 9d5a040840..6fe41a4828 (1512947:1517419) 2025-09-18 danilchap@webrtc.org Update test implementations of the PacketSocketFactory to newer api 2025-09-18 danilchap@webrtc.org Use propagated clock in AudioReceiveStream 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:419412821 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I21a4798177f990331dadf33a911a7a0886a1f137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6967901 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@{#1517694}
ChromiumChromium 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.