Commit 787483df authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Catapult from e6867ba7c785 to 57186883cdf3 (1 revision)

https://chromium.googlesource.com/catapult.git/+log/e6867ba7c785..57186883cdf3

2020-06-23 jbudorick@chromium.org devil: temporarily continue accepting blacklist in HealthyDevices.

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:1097306
Tbr: nuskos@google.com
Change-Id: Iff439e98ad53c4dce1be6e8edf216f5dd2c933ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261065Reviewed-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@{#781643}
parent a23a4b7e
......@@ -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': 'e6867ba7c78581349ab5e69d4a2dbb2c7198f57b',
'catapult_revision': '57186883cdf396ed9e9d9ce9863518a055909b4c',
# 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