commit | 0d5fdf271a4757cae457205b3c881fcdf1d2bba8 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Apr 07 17:37:26 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 07 17:37:26 2025 |
tree | c16f3fd1bc0152d322266dece2e7611b64f2347f | |
parent | 1cb1a463b1c1f56f143dec9fc9a24859f84c05d1 [diff] |
Roll DevTools Frontend from 6b1d718cf23d to 3b6a4060c03f (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/6b1d718cf23d..3b6a4060c03f 2025-04-07 jacktfranklin@chromium.org RPP: force a new AI conversation with a new trace file 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: None Change-Id: I1289246abaa10a3c2c6f3746621919efd17dd792 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6437344 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@{#1443601}
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.