diff options
| author |  Max Moroz <dor3s1@gmail.com> | 2018-08-20 06:42:45 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2018-08-20 06:42:45 -0700 |
| commit | 4574ff8bdbc5bf6f1197fa828e59fc2a2b6db797 (patch) | |
| tree | 6257dfcf7053b5290b5a5394b0d2bc50f85c0ea9 /docs | |
| parent | 05e6eee95ce4786c7ed130f6757c1a69089a5b73 (diff) | |
[infra] Add the build configuration and other pieces for clang code coverage. (#1547)
* [infra] Add the build configuration and other pieces for clang code coverage.
* Address the initial feedback, still a draft with some pieces missing.
* Trying to test things locally.
* Work in progress, now able to test the build process.
* Rebase and fix a comment.
* Figure out how to upload report, but still have issues with GCS access.
* Remove unnecessary debug prints.
* WIP: adding targets list reading + minor clean up.
* WIP
* WIP: now it works end to end but is very dirty and has limitations.
* WIP: use rsync -r -d to overwrite older reports (if any)
* WIP: trying to use a helper script for bulk corpus download.
* WIP: download corpus in batches passed via args.
* WIP: testing corpus downloading in batches.
* WIP: woohoo, now it works!
* Some cleanup for a high level review.
* Address review comments and add FAQ entry.
* Update FAQ.md as per comments by Oliver.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/faq.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/faq.md b/docs/faq.md index f040f2a2..f8e24ea2 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -93,6 +93,12 @@ If your fuzz target is running for many days and does not find bugs or new cover In either case, look at the [coverage reports](clusterfuzz.md#coverage-reports) for your target(s) and figure out why some parts of the code are not covered. +## Why are code coverage reports public? + +We work with open source projects and try to keep as much information public as +possible. We believe that public code coverage reports do not put users at risk, +as they do not indicate the presence of bugs or lack thereof. + ## What happens when I rename a fuzz target ? If you rename your fuzz targets, the existing bugs for those targets will get closed and fuzzing will start from scratch from a fresh corpora (seed corpus only). Similar corpora will get accumulated over time depending on the number of cpu cycles that original fuzz target has run. If this is not desirable, make sure to copy the accumulated corpora from the original fuzz target (instructions to download [here](corpora.md#downloading-the-corpus)) and restore it to the new GCS location later (instruction to find the new location [here](corpora.md#viewing-the-corpus-for-a-fuzz-target)). |