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

Roll Catapult from 35c950b7e18e to 4f894cfb70fd (1 revision)

https://chromium.googlesource.com/catapult.git/+log/35c950b7e18e..4f894cfb70fd

2020-06-30 bsheedy@chromium.org Reland "[Telemetry] Fix CrOS remote screenshots"

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:1098450,chromium:1098485
Tbr: wenbinzhang@google.com
Change-Id: I54920c990d3346fe37ed4d5682024eef10e52bec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276544Reviewed-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@{#784156}
parent 07d86c7b
......@@ -251,7 +251,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': '35c950b7e18eb5ab14ac34a3197bc2e7f374c60a',
'catapult_revision': '4f894cfb70fdd8fc7073b3f3d1857d0741f81452',
# 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