Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

test: add fuzzing set up#1497

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.

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

Already on GitHub?Sign in to your account

Open
DavidKorczynski wants to merge1 commit intocoveragepy:main
base:main
Choose a base branch
Loading
fromDavidKorczynski:add-fuzzer-setup

Conversation

@DavidKorczynski
Copy link

This is an effort to migrate fuzzers from OSS-Fuzz to upstream.

I've added it such that it's also a unit test that is run by way of pytest. The reason for doing so is to make it easier to test that the fuzzers won't break during development.

If you are interested in this addition, then I can refine the build script on the OSS-Fuzz side (https://github.com/google/oss-fuzz/blob/master/projects/coveragepy/build.sh) such that it builds all files prefixedtest_fuzz in the tests/ directory as fuzzers and will run them on OSS-Fuzz accodingly. This will make it trivial to add new fuzzers to the continuous fuzzing set up.

Ref:

Signed-off-by: David Korczynskidavid@adalogics.com

Signed-off-by: David Korczynski <david@adalogics.com>
"data",
[
b"random_data",
b"more random data"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I don't understand how atheris works. What does it do with these two data strings?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I only added these strings just to make it such that the fuzzer could be tested with pytest -- to e.g. check that the fuzzer won't break.

The data frompytest.mark.parametrize( is not used in the actual fuzzing runs.

@ProsperousHeart
Copy link
Contributor

Are this and#1490 still valid?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nedbatnedbatnedbat left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@DavidKorczynski@ProsperousHeart@nedbat

[8]ページ先頭

©2009-2025 Movatter.jp