commit | 2730779eb775ca9638a226fd7ac4a412761b4bbb | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sat Feb 08 01:41:12 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Feb 08 01:41:12 2025 |
tree | cc107071ae77f3e5d00910beab81e40177ad7dfb | |
parent | b39f0a8e5715d3b89e286b319b93399427b63752 [diff] |
Roll DevTools Frontend from 0cc1cdd5f8d1 to dced8d2f1f4e (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0cc1cdd5f8d1..dced8d2f1f4e 2025-02-08 cjamcl@chromium.org [RPP] Actually include url-level breakdown in ThirdParties insight If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@rotations.google.com,liviurau@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://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 Bug: chromium:388723721 Change-Id: I39777809f902e913a6d040e99e7a19e2731cfd4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6245834 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@{#1417669}
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.