commit | e92bf0cfd6bf0227a497694164308a06aa8281d4 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sun Apr 13 20:56:09 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Apr 13 20:56:09 2025 |
tree | fab31e27ebdf216b5663348cd9b616aa58f4c296 | |
parent | c3caab6bd7fe63503e30c0348dd9adf9a2b6f954 [diff] |
Roll Perfetto from 4c920851b488 to 9ddf987d48cd (1 revision) https://chromium.googlesource.com/external/github.com/google/perfetto.git/+log/4c920851b488..9ddf987d48cd 2025-04-13 rsavitski@google.com docs: track-event: fix missing instant event name in example + misc fixups (#1258) 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 oksamyt@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: chromium:410329414 Tbr: oksamyt@google.com,perfetto-bugs@google.com Change-Id: I7ac156b114a71f0f422afc2f0d7cb8e6fddd087a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6452572 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@{#1446337}
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.