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

[docs] Production testing 5: update "libFuzzer and AFL" page. #73

Merged
merged 0 commits into from Feb 5, 2019
Merged

Conversation

Dor1s
Copy link
Contributor

@Dor1s Dor1s commented Feb 4, 2019

No description provided.

@Dor1s
Copy link
Contributor Author

Dor1s commented Feb 4, 2019

I think we have a little problem here. It's not clear that this particular page refers to the local workflow, and I think it's good. It explains the basics of setting up a job for coverage guided fuzzing. I've added some pointers to make sure readers could jump to the production setup page (because they might've come here from there).

However, there is one more thing I want to add. An example with 3 jobs (afl asan, libfuzzer asan, libfuzzer ubsan) demonstrating how different env variables should be specified. Without this, it's gonna be very hard to understand. Question: should I include that example here, or on the production setup page, or create a new one? I'm leaning towards this one.

@jonathanmetzman
Copy link
Collaborator

For the record, there's a bit of overlap between this CL and #58

@Dor1s Dor1s merged this pull request into master Feb 5, 2019
@oliverchang oliverchang deleted the prod5 branch February 5, 2019 19:18
oliverchang pushed a commit that referenced this pull request Feb 5, 2019
* [docs] Production testing 5: update "libFuzzer and AFL" page.

* Fix a broken link.

* Make it more explicit how to edit a particular fuzzer.

* Change "this instruction" to "these instructions" as per comment from Jonathan.

* Address more review feedback.

* Add CUSTOM_BUILD = False for the contunuous build setup.

* Use fewer backticks and more bold double quotes!
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.

None yet

3 participants