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

Roll Catapult from 26ea611a4edb to 0dca23916904 (1 revision)

https://chromium.googlesource.com/catapult.git/+log/26ea611a4edb..0dca23916904

2020-08-18 jleconte@google.com 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: I1cd4d9e70c4be9d06b57bfcf15a6ef8af8324307
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360428Reviewed-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@{#799036}
parent 4ac03cb7
......@@ -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': '26ea611a4edbffea23e4ad28887dba209c7f7d50',
'catapult_revision': '0dca23916904f0bb7d03ae71b0ad32a8e2f54704',
# 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