Google Git
Sign in
chromium / chromium / tools / build / e5bd9ec6ffc5dec913c2e1ee15de1d6f4bc660fc
commite5bd9ec6ffc5dec913c2e1ee15de1d6f4bc660fc[log] [tgz]
authorSarah Mashayekhi <sarahmashay@google.com>Thu Dec 10 19:45:22 2020
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Dec 10 19:45:22 2020
tree8dae82b6a29563404c1be6979f0249485cfee87b
parentd182970089dfe081691a0085d82c89d42b9acf38 [diff]
Add cts step to tint recipe

Added to linux 64 try bot only, to avoid breaking them all.

Change-Id: If6754d03a9a2f48398573d073a082beef55f964e
Bug: tint:271
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2476956
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Dan Sinclair <dsinclair@google.com>
Commit-Queue: Dan Sinclair <dsinclair@google.com>
1 file changed
tree: 8dae82b6a29563404c1be6979f0249485cfee87b
  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.