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

Roll Catapult from e2dfd01ded55 to b60eeeee9ddb (1 revision)

https://chromium.googlesource.com/catapult.git/+log/e2dfd01ded55..b60eeeee9ddb

2020-10-13 jleconte@google.com Partially Revert: Fix 'Unknown git hash' when repository is not chromium.

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 nuskos@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:1133649
Tbr: nuskos@google.com
Change-Id: I3e319a236abac20a5461b449ea6a9346f2d71882
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465727Reviewed-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@{#816548}
parent e9b623cf
......@@ -254,7 +254,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': 'e2dfd01ded55dc5623be0b17cfb5655b78bf4ecd',
'catapult_revision': 'b60eeeee9ddbdf6b2390c9c2132fc2613643d2e7',
# 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