Skip to content

_content/doc/security/fuzz: update OSS-Fuzz documentation #334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

_content/doc/security/fuzz: update OSS-Fuzz documentation #334

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions _content/doc/security/fuzz/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,8 +85,9 @@ issues that would already be caught by an existing test.

Note that it is up to you to decide how long to run fuzzing. It is very possible
that an execution of fuzzing could run indefinitely if it doesn't find any errors.
There will be support to run these fuzz tests continuously using tools like OSS-Fuzz
in the future, see [Issue #50192](/issue/50192).
You can run these fuzz tests continuously using tools like OSS-Fuzz. See
[OSS-Fuzz](https://google.github.io/oss-fuzz/) for more information on setting up
continuous fuzzing for your project.

**Note:** Fuzzing should be run on a platform that supports coverage
instrumentation (currently AMD64 and ARM64) so that the corpus can meaningfully
Expand Down