commit | 30ef1ab581c48d8102bc60cfe578491e10f7ebbb | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Sep 25 17:00:38 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 25 17:00:38 2024 |
tree | c43f0a2ee55495180c439e7001c78046e0c81e59 | |
parent | 3e2ad5da43f2ceff9883a658766860ae1c571aeb [diff] |
Roll Crossbench from 5e1ae1f85dc5 to 49f2cd14ef51 (3 revisions) https://chromium.googlesource.com/crossbench.git/+log/5e1ae1f85dc5..49f2cd14ef51 2024-09-25 cbruni@chromium.org Harden android flag restoration 2024-09-25 cbruni@chromium.org Address various pylint issues all over the place 2024-09-25 khokhlov@google.com Fix WPR in persist_server mode with multiple browsers If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/crossbench-chromium Please CC cbruni@google.com,crossbench@chromium.org,khokhlov@google.com on the revert to ensure that a human is aware of the problem. 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 Tbr: khokhlov@google.com Change-Id: I96d01031445f8fe8e8dd6eb99b2361d374ca394d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5890242 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@{#1360006}
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.