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

fuzz: add Decoder fuzzing #51

Merged
merged 1 commit into from
Jan 8, 2023
Merged

Conversation

Jorropo
Copy link
Contributor

@Jorropo Jorropo commented Jun 8, 2022

This uses the spec tests as seeding value.

@Jorropo Jorropo force-pushed the fuzzing branch 2 times, most recently from 69eb43f to 376e246 Compare June 8, 2022 08:18
@BigLep
Copy link

BigLep commented Nov 11, 2022

@Jorropo and @rvagg : should we get this merged?

Copy link
Member

@rvagg rvagg left a comment

Choose a reason for hiding this comment

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

fine by me, if they're run by our updated CI - maybe rebase to master and check that it's working?

This uses the spec tests as seeding value.
@Jorropo
Copy link
Contributor Author

Jorropo commented Jan 8, 2023

rebased and ran on my local computer

@Jorropo Jorropo merged commit c442d70 into multiformats:master Jan 8, 2023
@Jorropo Jorropo deleted the fuzzing branch January 8, 2023 21:58
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.

3 participants