NOTE color codes represent how CV sees tryjobs, e.g. running failed succeeded which isn't as granular as Buildbucket's statuses.

dart-internal/g3.dart-internal.try/g3-cbuild-try dart/try/analyzer-analysis-server-linux-try dart/try/analyzer-linux-release-try dart/try/benchmark-linux-try dart/try/dart2js-hostasserts-linux-d8-try dart/try/dart2js-hostasserts-linux-unsound-try dart/try/dart2js-linux-chrome-try dart/try/dart2js-minified-linux-d8-try dart/try/dart2js-unit-linux-x64-release-try dart/try/dart2wasm-linux-chrome-try dart/try/dart2wasm-linux-d8-try dart/try/ddc-linux-chrome-try dart/try/ddc-linux-chrome-unsound-try dart/try/front-end-linux-release-x64-try dart/try/front-end-nnbd-linux-release-x64-try dart/try/pkg-linux-release-try dart/try/vm-aot-linux-debug-x64-try dart/try/vm-aot-linux-debug-x64c-try dart/try/vm-aot-mac-release-arm64-try dart/try/vm-aot-mac-release-x64-try dart/try/vm-aot-obfuscate-linux-release-x64-try dart/try/vm-aot-optimization-level-linux-release-x64-try dart/try/vm-aot-win-debug-arm64-try dart/try/vm-aot-win-debug-x64-try dart/try/vm-aot-win-debug-x64c-try dart/try/vm-mac-debug-arm64-try dart/try/vm-win-release-x64-try