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

This reverts commit d18f34b375f52bf7b231d3ed5566b021d094f9a4.

Reason for revert: This CL is breaking the coverage bots.

Original change's 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.
> 
> Bug: 948885
> Change-Id: I972572aca711105466ddb0e9386fb48377991aac
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1593976
> Commit-Queue: Sajjad Mirza <sajjadm@chromium.org>
> Reviewed-by: Yuke Liao <liaoyuke@chromium.org>

TBR=robertocn@chromium.org,liaoyuke@chromium.org,sajjadm@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

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