| commit | 58b8720efe34aeb2f67b36f76c0a207d1b23ea5c | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Oct 09 13:01:34 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 09 13:01:34 2025 |
| tree | fe9f9e5348c41909b2ff5388430bf6c6b0c2cb04 | |
| parent | d98c69757fb5f8f8805b7102ea9ca7a064048f18 [diff] |
Roll Perfetto from 3c78c63c99a7 to 91d0f0014376 (1 revision) https://chromium.googlesource.com/external/github.com/google/perfetto.git/+log/3c78c63c99a7..91d0f0014376 2025-10-09 lalitm@google.com Revert "ui: Change legacy Tea name to Mint (#3233)" (#3234) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC etiennep@google.com,perfetto-bugs@google.com,primiano@chromium.org 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 Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: etiennep@google.com,perfetto-bugs@google.com Change-Id: I1420df5694dc2ea2c53d9fce2330abea638b8e05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7025181 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@{#1527462}
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.