In addition to the ANGLE try bots using Chrome, and the GPU.FYI bots, ANGLE has standalone testing on the Chrome infrastructure. Currently these tests are compile-only. This page is for maintaining the configurations that don't use Chromium. Also see the main instructions for ANGLE Wrangling.
It‘s the ANGLE team’s responsibility for maintaining this testing infrastructure. The bot configurations live in four different repos and six branches.
Continuous builders for every ANGLE revision are found on the CI console:
https://ci.chromium.org/p/angle/g/ci/console
Try jobs from pre-commit builds are found on the builders console:
https://ci.chromium.org/p/angle/g/try/builders
bugs.chromium.org/p/chromium/issues/entry?template=Build+Infrastructure:
chromium.googlesource.com/chromium/tools/build:
scripts/slave/recipes/angle.py with new the config../scripts/slave/recipes.py test train to update checked-in golden files. This might no longer be necessary.chrome-internal.googlesource.com/infradata/config:
configs/chromium-swarm/bots.cfg to map from the slaves requested in step 1 to the builder configured in step 2.chromium.googlesource.com/angle/angle:
infra/config/global/cr-buildbucket.cfg to add the new builder (to ci and try), and set the new config option.infra/config/global/luci-milo.cfg to make the builders show up on the ci and try waterfalls.infra/config/global/luci-scheduler.cfg to make the builders trigger on new commits or try jobs respectively.infra/config/cq.cfg to add the builder to the default CQ jobs (if desired).There are other places where configuration for ANGLE infra lives. These are files that we shouldn't need to modify very often:
chrome-internal.googlesource.com/infradata/config:
configs/luci-token-server/service_accounts.cfg (service account names)configs/chromium-swarm/pools.cfg (swarming pools)chromium.googlesource.com/chromium/tools/depot_tools:
recipes/recipe_modules/gclient/config.py (gclient config)