commit | 902e59d49a065c9daaec4ecd2e2447c68786d3f1 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Feb 16 19:22:21 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 16 19:22:21 2022 |
tree | c55eb219230c3c3bc78f511d8c714e7e384a2924 | |
parent | 848f35dab97b297664a4e42b18ddbd62ededf909 [diff] |
Roll Perfetto from 7a348363a0c5 to 6c72ed07d1dd (2 revisions) https://android.googlesource.com/platform/external/perfetto.git/+log/7a348363a0c5..6c72ed07d1dd 2022-02-16 lalitm@google.com Merge "perfetto: add exports for targets with import public decls" 2022-02-16 lalitm@google.com Merge "perfetto: improve bazel BUILD file generation with protos" 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: I50506a1542b59296a4ceb65746aa9c9020553aa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3469061 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@{#971978}
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.