Forcefully enable resultdb in led_recipes_tester

After change crrev.com/c/2490615, now led allows to enable resultdb forcefully. Update the recipe accordingly.

Bug: 1141272
Change-Id: I4294d8680a571417ade3d4814c97962989bfc529
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2495564
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Chan Li <chanli@chromium.org>
6 files changed
tree: e225df3f6b9c48117932c96f28764b43eb23e6d5
  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.