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

Roll Catapult from a8af6641ce8e to 14ca9390e34a (1 revision)

https://chromium.googlesource.com/catapult.git/+log/a8af6641ce8e..14ca9390e34a

2020-07-29 dberris@chromium.org Revert "auto-triage: Revision range url support non-chromium revision"

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 eseckler@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:1106244
Tbr: eseckler@google.com
Change-Id: I987e4fa0e2243998b9eedc32cb1af7e45101fa31
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2325903Reviewed-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@{#792668}
parent 678ae343
......@@ -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': 'a8af6641ce8e151b93a95e782c77f1e884a99098',
'catapult_revision': '14ca9390e34a03dc5723e202d330978635666c95',
# 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