commit | eec7ba2dce6a95b1fb6baaaeb26fd35f511b7563 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Jan 16 18:31:29 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 16 18:31:29 2023 |
tree | 876e1b26b05adb628395a8bf0fb73c9433839f89 | |
parent | d53fa9026d1cfe7d6c81317406ef236289cfd787 [diff] |
Roll Perfetto from abec7d5c29c7 to 845a57f7e300 (2 revisions) https://android.googlesource.com/platform/external/perfetto.git/+log/abec7d5c29c7..845a57f7e300 2023-01-16 rsavitski@google.com Merge "perfetto: Replace emplace with emplace_hint" 2023-01-16 lalitm@google.com Merge "tp: Implement support for different out strings" 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: I2eff8a40dab6221e3142a4051aa944ac7aeae28b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4169177 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@{#1093108}
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.