I was wondering if you would like to integrate continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and in this PR https://github.com/google/oss-fuzz/pull/8303 I did an initial integration into OSS-Fuzz where the current fuzzer targets the scalar functions and move_median using an array generated from fuzzer data. The fuzzing engine used by OSS-Fuzz is Atheris.
The native code is compiled with various sanitizers in order to detect memory corruption issues. Additionally, the code has various asserts to trigger in the event any inconsistency between scalar and .slow.. functions.
If you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.
Hi,
I was wondering if you would like to integrate continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and in this PR https://github.com/google/oss-fuzz/pull/8303 I did an initial integration into OSS-Fuzz where the current fuzzer targets the scalar functions and
move_medianusing an array generated from fuzzer data. The fuzzing engine used by OSS-Fuzz is Atheris.The native code is compiled with various sanitizers in order to detect memory corruption issues. Additionally, the code has various asserts to trigger in the event any inconsistency between scalar and
.slow..functions.If you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.