| commit | 150461b15b9dac164eda3c55a0ab15f2b8cbe935 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Aug 11 23:40:24 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 11 23:40:24 2025 |
| tree | e6a0d5bbc784780b68232ed47e325435de17ab63 | |
| parent | 84b50edb598b5b0758f6df0dc1af881ca30a5542 [diff] |
Roll FuzzTest from 9598f9003440 to d08c25063b88 (1 revision) https://chromium.googlesource.com/external/github.com/google/fuzztest.git/+log/9598f9003440..d08c25063b88 2025-08-11 yamilmorales@google.com Revert HasDefaultFlag: Some instrumentation behaviors were enabled by default causing test failures If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuzztest-chromium Please CC chrome-fuzzing-core@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://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 Cq-Include-Trybots: luci.chromium.try:linux-centipede-asan-rel;luci.chromium.try:linux-libfuzzer-asan-rel;luci.chromium.try:win-libfuzzer-asan-rel Bug: None Tbr: chrome-fuzzing-core@google.com Change-Id: Iad64b359d5f0a3673be3eb404103e9dfd38de26b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6839501 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@{#1499883}
ChromiumChromium 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.