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

[libcasr] cargo-fuzz support #132

Merged
merged 7 commits into from
Sep 16, 2023
Merged

[libcasr] cargo-fuzz support #132

merged 7 commits into from
Sep 16, 2023

Conversation

anfedotoff
Copy link
Collaborator

No description provided.

libcasr/fuzz/fuzz_targets/parse_stacktrace.rs Show resolved Hide resolved
libcasr/Cargo.toml Show resolved Hide resolved
libcasr/fuzz/fuzz_targets/parse_stacktrace.rs Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
Fix format
@SweetVishnya
Copy link
Collaborator

Does cargo fuzz has non-zero exit code when crash is found?

@anfedotoff
Copy link
Collaborator Author

Does cargo fuzz has non-zero exit code when crash is found?

Yes, I checked non-zero exit code is returned.

@SweetVishnya
Copy link
Collaborator

Does cargo fuzz has non-zero exit code when crash is found?

Yes, I checked non-zero exit code is returned.

The only thing left then is to collect some starting corpus.

@SweetVishnya
Copy link
Collaborator

Can we move fuzzing to a separate pipeline? Thus, it can be run in parallel with tests. And CI will take less time.

@anfedotoff anfedotoff merged commit c229bed into master Sep 16, 2023
1 of 4 checks passed
@anfedotoff anfedotoff deleted the fuzz branch September 16, 2023 14:12
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.

4 participants