Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refs #12442 - generate a fuzzing corpus by extracting code from testrunner #7232

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

firewave
Copy link
Collaborator

No description provided.

@firewave
Copy link
Collaborator Author

I tried to do this via an option. It would be possible to pass this as an internal field via the Settings but it would be problematic to get that into all Settings objects in the tests.

@firewave
Copy link
Collaborator Author

The idea is to have a corpus generated from all our test cases which will generate an artifact which can be pulled from the OSS-Fuzz integration to be used. This will give us a broad spectrum of code.

Some of the files are rather big though and I wonder if we should filter those out since they could provide misleading timeouts and too big inputs. But that could also be handled by specify the maximum input size via a fuzzing CLI parameter.

@firewave firewave force-pushed the testrunner-dump branch 5 times, most recently from 150a1b8 to 1e619f4 Compare January 17, 2025 17:14
@firewave firewave changed the title generate a fuzzing corpus by extracting code from testrunner refs #12442 - generate a fuzzing corpus by extracting code from testrunner Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant