commit | 330a199837423dd309ae9c76d93c51162b68cc26 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Oct 13 12:50:55 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 13 12:50:55 2022 |
tree | 8d9e251741d00e11fd26748716e1087f889bf9fb | |
parent | 2f941efd2f5ce48463eb9abeabd1e7f8ead714d4 [diff] |
Roll WebRTC from d1196636dc72 to 036b3fdea280 (2 revisions) https://webrtc.googlesource.com/src.git/+log/d1196636dc72..036b3fdea280 2022-10-13 phancke@microsoft.com Reland "stats: migrate to Timestamp" 2022-10-13 perkj@webrtc.org Parameterize some PCFullStackTest and run with reduced number of threads. 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 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug 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: Iab75a2cbae106505848a3927f4238b1a8acbc9fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3952331 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@{#1058648}
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.