commit | 2b54bc6ac6d5e0347191328066cf14f8418ce8cc | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Mar 08 23:07:25 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 08 23:07:25 2022 |
tree | 05b876b3c60c579af1524ef9d3d819e14546299b | |
parent | a301c90f0ec2ba4de353d43d9000bbdd70590ef3 [diff] |
Roll Perfetto from 69e7f7d0643c to 504b4099476a (2 revisions) https://android.googlesource.com/platform/external/perfetto.git/+log/69e7f7d0643c..504b4099476a 2022-03-08 hjd@google.com Merge "Release contents of aosp/2010697 to stable" 2022-03-08 treehugger-gerrit@google.com Merge "bazel: remove public visibility for intermediate proto targets" 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 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug 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: I8062f59959e6e08eb0707ab6e815fc1137988c10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3511108 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@{#978931}
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.