Commit 2d4a29a8 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Catapult from ac95abdb4b12 to 420f7362d68a (1 revision)

https://chromium.googlesource.com/catapult.git/+log/ac95abdb4b12..420f7362d68a

2020-11-12 wenbinzhang@google.com [benchmarking] skip finding possible browser if it is found already

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 zhanliang@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:1013630
Tbr: zhanliang@google.com
Change-Id: I0880a9872ca13ba201b1ce66e7c721a0600c41b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533166Reviewed-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@{#827072}
parent 01caa0e7
......@@ -264,7 +264,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': 'ac95abdb4b129e77ae3a70095c68498b4ed4a375',
'catapult_revision': '420f7362d68aec3bb885db27e79f0636a1d111a9',
# 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