[devtools] Postpone usage of the new --no-html-coverage flag

Introducing this flag in the recipe too early will break beta and stable.
The flag just prevents unnecessary generation of an html report, so it is not critical.

TBR=tmrts@chromium.org

Change-Id: I6b6fac4daf192beb51d2358b93b44443c09de08a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2550382
Reviewed-by: Liviu Rau <liviurau@chromium.org>
Commit-Queue: Liviu Rau <liviurau@chromium.org>
7 files changed
tree: cfdfc62c1738ccc4297a7a975c4b344e8c55006b
  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.