* [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.
* [infra] helper.py: support "profile" command for a single fuzz target with arbitrary corpus location.
* Address review feedback.
* Update code_coverage.md page.
* [infra] Fix helper.py as per feedback from @evverx + fix issues from #1519.
* Remove stuff from local testing
* Suppress unnecessary output from GSUtil.
* [infra] Enable clange code coverage reports generation for local runs.
* Use runner image and move corpus management to the helper.py
.
* Clean up, delete unnecessary stuff, add comments.
* Run fuzz targets in parallel. Do not exit in case of an error.
* Address review feedback, except of the threading thing.
* Fix a typo.
* Use ThreadPool implementatino available in standard python2.7 package.
* Add dry run support + no corpus download option.
* Fix flags handling + add log output in case of an error.
* Append arguments for fuzz target instead of replacing them.
* Remove dry run functionality as it currently errors out after two runs.
* Fix some spacing in the code.
* Update documentation regarding new code coverage script.
* [docs] Clean up the conflicts in reproducing.md.
* Add engine arg everywhere + move bad build checks instruction back to the bottom
* Remove enginge argument from instructions not related to build checks
While trying to get a coverage report for a new project (Envoy),
building with the coverage sanitizer seemed necessary to get the
coverage files dumped.
Signed-off-by: Harvey Tuch <htuch@google.com>