commit | d0c85d4f905d2a23f6c7f565e643cdba8d9c0077 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Dec 08 14:39:53 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 08 14:39:53 2023 |
tree | 92899ea59323ddc73346c2b840ec3d4b4055636c | |
parent | 67ef96b3b0d1d6968e0ec1d09c8be0d5ee03357d [diff] |
Roll Perfetto from a02c9d3895b5 to 594f22e0cfb4 (2 revisions) https://android.googlesource.com/platform/external/perfetto.git/+log/a02c9d3895b5..594f22e0cfb4 2023-12-08 stevegolton@google.com Merge "[ui] Fixed some merge issues regarding uri and track keys." into main 2023-12-08 stevegolton@google.com Merge "[ui] Removed unrelated functionality from frontendLocalState." into main 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 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: perfetto-bugs@google.com Change-Id: I16fc8015f5fc54f02f4d81e83cdfbf1a0cb8932b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5103617 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@{#1235009}
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.