Run Dawn CQ with ToT Dawn.

Without this Dawn's CQ GPU builders try to apply the patch being
tested on the version of Dawn that's in Chromium's DEPS instead of
ToT Dawn, causing failures when patches don't apply.

This will cause all these builders to use ToT Dawn:
 - Dawn's CQ GPU builders (the reason why this is needed)
 - The GPU FYI waterfall
 - ANGLE's CQ GPU builders
 - GPU optional try builders

This is because all of the above are either the GPU FYI builders
or mirror them so they must all have the same config. It involves
some risk that Dawn will break compilation on one of the extra
builders but it is tiny because Dawn's CQ will be testing the same
configuration.

Bug: chromium:901830
Change-Id: Icc48e02ae1f83b9fd846438a250bd09fe5ab3b42
Reviewed-on: https://chromium-review.googlesource.com/c/1350854
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2 files changed
tree: c4058e340a11aa9f9e6401759b79dc27467d8f4c
  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.