Commit d34e93e7 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Catapult from 0dca23916904 to 6b30e90492c5 (1 revision)

https://chromium.googlesource.com/catapult.git/+log/0dca23916904..6b30e90492c5

2020-08-18 jleconte@google.com Revert "Chrome Perf Dashboard UI links to Monorail bugs are missing project id."

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC rmhasan@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1101773
Tbr: rmhasan@google.com
Change-Id: I0e49407d3b002c9251ebc8b66e54659e97be2063
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361787Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#799103}
parent a90465a1
......@@ -258,7 +258,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling catapult
# and whatever else without interference from each other.
'catapult_revision': '0dca23916904f0bb7d03ae71b0ad32a8e2f54704',
'catapult_revision': '6b30e90492c5fba4483a489d7f2b89fa0a1c39f7',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libFuzzer
# and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment