ToT Clang Coverage recipe reads build dir at runtime.

The recipe was previously hardcoded to assume the build dir would be
named "Release", which is not always true. Now it reads the correct
path from the chromium module.

Bug: 1090653
Change-Id: Idbeeb24bfe5d6d2d4dd6def784f1ff43d558fc7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2523678
Commit-Queue: Sajjad Mirza <sajjadm@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Auto-Submit: Sajjad Mirza <sajjadm@chromium.org>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
2 files changed
tree: 729754cfb028cc46682ea3763acdc3bea54b191e
  1. infra/
  2. recipes/
  3. scripts/
  4. site_config/
  5. third_party/
  6. .gitattributes
  7. .gitignore
  8. .style.yapf
  9. .vpython
  10. .yapfignore
  11. codereview.settings
  12. CROS_OWNERS
  13. DEPS
  14. environment.cfg.py
  15. LICENSE
  16. OWNERS
  17. PRESUBMIT.py
  18. README.md
  19. WATCHLISTS
README.md

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.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.