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.

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

Jump to bottom

Continuous fuzzing through OSS-fuzz #309

Closed
AdamKorcz opened this issue Feb 4, 2021 · 1 comment
Closed

Continuous fuzzing through OSS-fuzz #309

AdamKorcz opened this issue Feb 4, 2021 · 1 comment
Assignees
@derobins
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Task Actions that don't fit into any other type category

Comments

@AdamKorcz
Copy link

I have been working on setting up continuous fuzzing of hdf5 by way of Libfuzzer and OSS-fuzz.

Fuzzing of hdf5 has been discussed here: #263 (comment) and here: #272.

Tagging @schwehr since you suggested integrating with OSS-fuzz.

I have set up a draft integration over at OSS-fuzz here: google/oss-fuzz#5103.
Feel free to leave any comments over there.

It is free to integrate with OSS-fuzz, and it is expected that bugs are fixed, so that the resources spent on fuzzing hdf5 go towards resolving bugs in the code base.

To finish the integration, at least one maintainers email is needed for bug reports.

I recommend moving the fuzzer and the build script upstream to easier maintain them.
@emmenlau emmenlau mentioned this issue May 7, 2021
Closed
@derobins derobins self-assigned this May 27, 2022
@derobins derobins added Priority - 1. High 🔼 These are important issues that should be resolved in the next release Component - Testing Code in test or testpar directories, GitHub workflows Type - Task Actions that don't fit into any other type category labels May 3, 2023
@derobins
Copy link
Member

derobins commented Oct 9, 2023

We're set up to use oss-fuzz now

@derobins derobins closed this as completed Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@derobins derobins

Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Task Actions that don't fit into any other type category
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@derobins @AdamKorcz