This repository has been archived by the owner on Jan 12, 2020. It is now read-only.
Introduce ClusterFuzz support #15
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Mar 10, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this series of commits I've now enabled clusterfuzz support for the project, running at https://bughunt.appspot.com/. The use of AFL is now removed in favor of cargo-fuzz/libFuzzer for easy compatibility with clusterfuzz. This has made the README instructions more straightforward, which hopefully will help new contributors to the project.
For reasons related, I think, to the travis org/com distinction the branch push builds -- done on org -- fail while the branch builds -- done on com -- succeed. This is a result of the secrets being pegged to com. I'll see after this is merged if I can sort out which domain the project will always run on.
The clusterfuzz setup consumes actual funds, though for now we're operating out of credits. This project will need to sort out funding at some point, if the clusterfuzz setup proves worth keeping.