| commit | 8b314e6fc1446df71d9e83f72554a8d306d613c1 | [log] [tgz] |
|---|---|---|
| author | Sajjad Mirza <sajjadm@google.com> | Mon May 13 18:16:56 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon May 13 18:16:56 2019 |
| tree | 15916b04f4e8db7dfd3e76502b4a772b06dba13a | |
| parent | f8de5c3ab6ea9d67b10d04b3a3eb105e60208d89 [diff] |
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>
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.
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.