commit | d5f83c0364d428ca4e3e5e17027a8f9c847f9620 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Feb 17 17:22:32 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 17 17:22:32 2025 |
tree | 9050cfe8d1d7d33c66f71b80908988e6848e2d3d | |
parent | 42cf26b433177bfb60b921f1831c0894d5c159ae [diff] |
Roll DevTools Frontend from 44861abac003 to a2b4cda20733 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/44861abac003..a2b4cda20733 2025-02-17 alexrudenko@chromium.org [cleanup] parametrize panel tests 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: Iec436fb8ee8f8fcf978955e07f13385b85794ae6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6277386 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@{#1421102}
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.