| commit | 3669f4844733cf35e1ac5ef16a9e3683f238c4dd | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Jul 26 14:30:05 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 26 14:30:05 2024 |
| tree | 37e635715feca3bc96156bef850e0b65362cc568 | |
| parent | 413b0ce00010160839a8105dc3ea53c513cb2f23 [diff] |
Roll Crossbench from 581d34990484 to e9227372f843 (1 revision) https://chromium.googlesource.com/crossbench.git/+log/581d34990484..e9227372f843 2024-07-26 cbruni@chromium.org Skip binary override test if python3 is not installed 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: Ib2d917544126facd2755d6d9bee4106c620e89cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5743424 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@{#1333538}
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.