commit | d45fe414864a8fde71d6dee3668aa8eacd6f6568 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Apr 22 10:11:18 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 22 10:11:18 2025 |
tree | 6f1acb6876c46b5e9c5057f7fb4ff43efe27e97e | |
parent | 8e0a54950e29e5fa2d9dfe154e8bd528e3613553 [diff] |
Roll Crossbench from d51c8e968d54 to e15531aec5a0 (1 revision) https://chromium.googlesource.com/crossbench.git/+log/d51c8e968d54..e15531aec5a0 2025-04-22 cbruni@chromium.org Better handle browser config paths 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: I4bef21fd903bfc0f17043e4c5597cf5c188ad2e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6478616 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@{#1449826}
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.