Reland "Generate and upload separate coverage data for each target in a build."

Changed the name of the upload directory for per-target metadata so that
it doesn't conflict with where the merged metadata is uploaded.

Previous commit description:

Generate and upload separate coverage data for each target in a build.

This requires us to run llvm-cov on the profdata for each test target.
The code coverage service will aggregate the per-target data to make
reports.

Temporarily skipping this for fuzzers so that the builds don't hit the
20 hr time limit on swarming

Bug: 948885
Change-Id: I17794b6a9aac537b54a2c0c723545d73c37b5f68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1610557
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Sajjad Mirza <sajjadm@chromium.org>
3 files changed
tree: 15916b04f4e8db7dfd3e76502b4a772b06dba13a
  1. .gitattributes
  2. .gitignore
  3. .vpython
  4. DEPS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. WATCHLISTS
  10. codereview.settings
  11. environment.cfg.py
  12. infra/
  13. masters/
  14. scripts/
  15. site_config/
  16. slave/
  17. tests/
  18. third_party/
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.