commit | 2375b34b01b78feb5ad0a7e33b030a2110900b43 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Feb 10 23:53:37 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 10 23:53:37 2025 |
tree | 84523bfb54d17fa6ce5baee282d3b098e0270c1f | |
parent | aa4a766b2a2745795691c22198f744186b413e48 [diff] |
Roll FuzzTest from 4d83b86f7dea to fd9f91e96f8e (1 revision) https://chromium.googlesource.com/external/github.com/google/fuzztest.git/+log/4d83b86f7dea..fd9f91e96f8e 2025-02-10 lszekeres@google.com Fix bug when writing corpus file in the first time. 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: Ifc3e17c9c243e1080d16d71a1bd37634b55348d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6249969 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@{#1418338}
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.