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

chrome/try/linux-chromeos-compile-chrome chrome/try/linux-perf-trigger chrome/try/win-branded-compile-rel chromium/try/android-arm64-rel chromium/try/android-binary-size chromium/try/android-cronet-arm-rel chromium/try/android-desktop-x64-rel chromium/try/android-x64-rel chromium/try/android-x86-rel chromium/try/android_compile_dbg chromium/try/chromeos-amd64-generic-rel-gtest chromium/try/chromeos-arm64-generic-rel chromium/try/chromeos-js-coverage-rel chromium/try/chromium_presubmit chromium/try/compile-size chromium/try/fuchsia-binary-size chromium/try/fuchsia-x64-cast-receiver-rel chromium/try/ios-simulator chromium/try/linux-chromeos-compile-dbg chromium/try/linux-chromeos-rel chromium/try/linux-full-remote-rel chromium/try/linux-js-coverage-rel chromium/try/linux-libfuzzer-asan-rel chromium/try/linux-rel chromium/try/linux-wayland-mutter-rel chromium/try/linux_chromium_asan_rel_ng chromium/try/linux_chromium_compile_dbg_ng chromium/try/linux_chromium_tsan_rel_ng chromium/try/mac-rel chromium/try/mac_chromium_compile_dbg_ng chromium/try/win-arm64-compile-dbg chromium/try/win-libfuzzer-asan-rel chromium/try/win-presubmit chromium/try/win-rel chromium/try/win_chromium_compile_dbg_ng