commit | fd8f786805eeeef8fb9c43b271ba3147284bb6aa | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Mar 11 16:46:38 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 11 16:46:38 2025 |
tree | b534ded028bf720d5638a7ed303c0be0a13a3e5b | |
parent | 262ca1235e14100b2a79b5a5484dd10cbb364fa8 [diff] |
Roll FuzzTest from f06a6a56457c to 75dc8d63f97a (1 revision) https://chromium.googlesource.com/external/github.com/google/fuzztest.git/+log/f06a6a56457c..75dc8d63f97a 2025-03-11 fuzztest@google.com Forcibly terminate the runner via if the previous watchdog abort attempt has timed out. 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: I9d4e6bcd6f7ea18c9df1a672647cd611e603ebd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6343930 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@{#1430939}
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.