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

chromium-m132/try/android-arm64-rel chromium-m132/try/android-binary-size chromium-m132/try/android-cronet-arm-rel chromium-m132/try/android-x64-rel chromium-m132/try/android-x86-rel chromium-m132/try/android_compile_dbg chromium-m132/try/chromeos-amd64-generic-rel-gtest-and-tast chromium-m132/try/chromeos-arm64-generic-rel chromium-m132/try/chromium_presubmit chromium-m132/try/fuchsia-binary-size chromium-m132/try/fuchsia-x64-cast-receiver-rel chromium-m132/try/ios-simulator chromium-m132/try/ios-simulator-full-configs chromium-m132/try/linux-chromeos-compile-dbg chromium-m132/try/linux-chromeos-rel chromium-m132/try/linux-libfuzzer-asan-rel chromium-m132/try/linux-rel chromium-m132/try/linux_chromium_asan_rel_ng chromium-m132/try/linux_chromium_compile_dbg_ng chromium-m132/try/linux_chromium_tsan_rel_ng chromium-m132/try/mac-rel chromium-m132/try/mac14-arm64-rel chromium-m132/try/mac_chromium_compile_dbg_ng chromium-m132/try/win-arm64-compile-dbg chromium-m132/try/win-libfuzzer-asan-rel chromium-m132/try/win-rel chromium-m132/try/win_chromium_compile_dbg_ng