Commit 86ac7e19 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/skia 8f88b2da05d5..c573ec8ab233 (1 commits)

https://skia.googlesource.com/skia.git/+log/8f88b2da05d5..c573ec8ab233


git log 8f88b2da05d5..c573ec8ab233 --date=short --no-merges --format='%ad %ae %s'
2019-05-29 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).


Created with:
  gclient setdep -r src/third_party/skia@c573ec8ab233

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=kjlubick@google.com

Change-Id: I72c15ca410930959c0049ba1c96e2e5034cc6232
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633737Reviewed-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@{#664106}
parent b6bd8e69
......@@ -138,7 +138,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling Skia
# and whatever else without interference from each other.
'skia_revision': '8f88b2da05d542620a7e5d97aec917714b5cf8fc',
'skia_revision': 'c573ec8ab2337a8cff09c8bd881b18f118766ab3',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling V8
# 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