Relax the requirement that builder and tester configs are synced.

The code for looking up tester GN args has been implemented in a way
that doesn't require the builder and tester configs to be synced to
produce the correct results. Allowing the builder and tester to
deviate enables removing less than desirable code that was used for
disabling LSan when running the "Linux ASan Tests (sandboxed)"
tester. It is still generally desirable that the builder and tester
are synced, so the sync test has been relaxed to enable custom checks.

Change-Id: I562c77d205755c80c5df68a21f90064dc52caaeb
Reviewed-on: https://chromium-review.googlesource.com/c/1265736
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
9 files changed
tree: ad6765218d20e4cc4e52dd46c60fe9dd5b15fd99
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. .vpython
  11. codereview.settings
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

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.