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

ci: Store fuzzing corpus as artifact #333

Merged
merged 1 commit into from
May 25, 2020
Merged

ci: Store fuzzing corpus as artifact #333

merged 1 commit into from
May 25, 2020

Conversation

chfast
Copy link
Collaborator

@chfast chfast commented May 24, 2020

No description provided.

Copy link
Member

@axic axic left a comment

Choose a reason for hiding this comment

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

Assuming the goal here is to store the corpus so it can be inspected for reproduction, if needed.

@chfast
Copy link
Collaborator Author

chfast commented May 25, 2020

Assuming the goal here is to store the corpus so it can be inspected for reproduction, if needed.

Yes. I wanted to check why it had not found the bug in #334. Current fuzzer is pretty weak.
You can also download the corpus from CI and merge with a one you have locally.

@chfast chfast merged commit 8011def into master May 25, 2020
@chfast chfast deleted the ci_corpus branch May 25, 2020 10:24
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.

2 participants