Commit 11e6066a authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Catapult from 15d5f65efa22 to 92c6c3ec3b9b (1 revision)

https://chromium.googlesource.com/catapult.git/+log/15d5f65efa22..92c6c3ec3b9b

2020-06-04 fancl@chromium.org auto-bisect: Prevent auto-bisection starting on the same alerts

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 wenbinzhang@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:1091079
Tbr: wenbinzhang@google.com
Change-Id: I84da92ce8233f79e6d4c1146d587c5204584532c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2229547Reviewed-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@{#775007}
parent 45c6975a
......@@ -245,7 +245,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': '15d5f65efa22587edf01e9c1b922bb32807c46ed',
'catapult_revision': '92c6c3ec3b9bd8c5bd2182c62b0f6c2cfaabbad9',
# 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