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/benchmark-linux-try dart/try/front-end-linux-release-x64-try dart/try/pkg-linux-release-try dart/try/vm-aot-android-release-arm64c-try dart/try/vm-aot-android-release-arm_x64-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-appjit-linux-debug-x64-try dart/try/vm-asan-linux-release-x64-try dart/try/vm-checked-mac-release-arm64-try dart/try/vm-eager-optimization-linux-release-ia32-try dart/try/vm-eager-optimization-linux-release-x64-try dart/try/vm-ffi-android-debug-arm-try dart/try/vm-ffi-android-debug-arm64c-try dart/try/vm-ffi-qemu-linux-release-arm-try dart/try/vm-ffi-qemu-linux-release-riscv64-try dart/try/vm-linux-debug-ia32-try dart/try/vm-linux-debug-x64-try dart/try/vm-linux-debug-x64c-try dart/try/vm-mac-debug-arm64-try dart/try/vm-mac-debug-x64-try dart/try/vm-msan-linux-release-x64-try dart/try/vm-reload-linux-debug-x64-try dart/try/vm-reload-rollback-linux-debug-x64-try dart/try/vm-ubsan-linux-release-x64-try dart/try/vm-win-debug-arm64-try dart/try/vm-win-debug-x64-try dart/try/vm-win-release-ia32-try dart/try/vm-win-release-x64-try