commit | ce68d70b946a03dc7b9950aa82bfe9c8b28899f6 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri May 02 18:48:24 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 02 18:48:24 2025 |
tree | a6f903ea3cd739f4b06719e2007b346bcba1d7c4 | |
parent | 7bfdaa4ae4b57a1c002043f2b765b5fbaf51cfd5 [diff] |
Roll DevTools Frontend from c37b39f52e7e to 5f8f9e5c538a (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c37b39f52e7e..5f8f9e5c538a 2025-05-02 andoli@chromium.org Disable flaky perf panel recording e2e test 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:415305960 Change-Id: I940af462aa25af0d84a5b7d3f545412c4d45f168 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6507701 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@{#1455116}
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.