Enable 'use_swarming_recipe_to_trigger' for chromium_fuzz and chromium_gpu_fyi builders

Checked a few builders in both files. They all have the
$recipe_engine/isolated property set. So I don't think https://crrev.com/c/2449672
will affect these builders.

Manually triggered luci.chromium.ci:Linux FYI Debug (NVIDIA):
https://chromium-swarm.appspot.com/task?id=4f14630a3dbcfe10

Bug: 894045
Change-Id: I36d7ee99d3c16e4f75fe203c832554ce7147c0ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2449675
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Ye Kuang <yekuang@google.com>
3 files changed
tree: fc1f14862a44944fdcadb7b22db89e150c8cc26b
  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.