| commit | 20567925655ca5c47ae13c1e20c18a9b56032306 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Jun 01 12:00:52 2021 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 01 12:00:52 2021 |
| tree | bbc19f7736a4c3203b3c264c7cd7543fb9ab899e | |
| parent | 2e80500e250894172348faf57bb181a134bd1c6c [diff] |
Roll Perfetto from bb3b66d48669 to 44702c57e7e6 (1 revision) https://android.googlesource.com/platform/external/perfetto.git/+log/bb3b66d48669..44702c57e7e6 2021-06-01 treehugger-gerrit@google.com Merge "Avoid invalid reads parsing begin print events" 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 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/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I03a25cd732c0b29d43b3d892e8f5c293e6521b56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2928325 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/master@{#887922}
ChromiumChromium 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.