* [infra] Use 'coverage' and 'fuzzing' tags to filter builds (follow-up #1547).
* Remove unintentional print call.
* Remove a variable that is not used anympre.
* [infra] Use coverage utils from Chromium and other fixes (follow-up #1547).
* Sort dependencies in an alpha order plus make more readable.
* Re-order arguments passed to coverage_helper script.
* Rename REPORT_DIR variable and put summary.json into platform specific dir.
* Fix -src-root-dir value.
* [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] profile command: do not fail hard if some fuzz targets have no corpus.
* Change listing to corpus_listing to be more explicit.
* Address review comment from Abhishek
* [infra] Add script for downloading a batch of corpus backups (for #1547).
* Add missing wget dependency and replace a tab with spaces.
* Convert more tabs to spaces.
When a fuzzer is seriously broken (which happens occasionally during debug),
it's unlikely to start properly let alone provide some meaningful
output. In this case, it seems reasonable to skip some checks and prevent bash
from encountering the following syntax error:
```
/usr/local/bin/bad_build_check: line 68: ((: < 100 : syntax error: operand expected (error token is "< 100 ")
```
* [infra] Add retry wrapper to LLVM checkout commands.
* Fix a typo.
* Clean up the retry wrapper as per discussion with Abhishek.
* Fix disabling / enabling exit-on-error mode, bash is hard!
* Fix a comment.
* Fix bad build check.
Bad build checks previously just checked that a file is an executable
ELF. This is insufficient because libraries are also executable ELFs.
Add a check that the file contains LLVMFuzzerTestOneInput, in order
to consider a fuzz target.
Also update coverage and test_report for consistency.
Max Moroz