c22967e74f
There's little need to run a Release ASAN bot when we've an equivalent Debug ASAN bot. This removes almost all Release ASAN bots and adds one Debug ASAN bot. The only Release ASAN bots I've kept are a bot on the CQ, Perf-Ubuntu18-Clang-Golo-GPU-QuadroP400-x86_64-Release-All-ASAN, and the corresponding Build bot. We could leave that forever, replace it with a Debug bot, or just take it off the CQ. Change-Id: Ic0864fe2efdc39a95e204c7dfaaace238f2098ed Reviewed-on: https://skia-review.googlesource.com/c/skia/+/262087 Commit-Queue: Mike Klein <mtklein@google.com> Reviewed-by: Brian Osman <brianosman@google.com> Reviewed-by: Ben Wagner aka dogben <benjaminwagner@google.com> |
||
---|---|---|
.. | ||
bots | ||
canvaskit | ||
cmake | ||
config | ||
cross-compile/docker/cross-linux-arm64 | ||
cts | ||
gcc | ||
lottiecap | ||
pathkit | ||
project-config | ||
skqp | ||
wasm-common | ||
README.md |
This directory contains infra-specific files. The branch-config/ directory contains configs that are specific to the master branch (e.g. config for the CQ committing to the master branch), while project-config/ directory contains project-wide configuration (e.g. list of buckets for cr-buildbucket service and list of refs known to the infra services).