You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
changed the title
generate a fuzzing corpus by extracting code from testrunner
refs #12442 - generate a fuzzing corpus by extracting code from testrunnerJan 17, 2025
If the code relies on additional files (i.e. includes) it would not work as expected. This suggests that we should move tests which require additional files from unit tests to Python.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
firewave
force-pushed
the
testrunner-dump
branch
6 times, most recently
from
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
No description provided.