commit | 4bb68ad1d2a58fce501c3e921c218470543f0c67 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Apr 03 20:59:05 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 03 20:59:05 2025 |
tree | 0e6e6b38ae0c0eab7254ce844df6022bc419d569 | |
parent | 7dda5c33b888448d11dbc4de9deabcaa1bc88848 [diff] |
Roll FuzzTest from 33bb3d2040f6 to 80eeef83f778 (1 revision) https://chromium.googlesource.com/external/github.com/google/fuzztest.git/+log/33bb3d2040f6..80eeef83f778 2025-04-03 xinhaoyuan@google.com Set input timeout and rss/stack limit in the environment for Centipede. 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: Ib437f6e0a920b248863dbd8685f64494e095a3db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6429001 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@{#1442413}
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.