Commit 789f0c99 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/skia 61d38ade8c1d..aefecad7c0d2 (1 commits)

https://skia.googlesource.com/skia.git/+log/61d38ade8c1d..aefecad7c0d2


git log 61d38ade8c1d..aefecad7c0d2 --date=short --no-merges --format='%ad %ae %s'
2019-03-15 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 6299cd6e..558a9829 (482 commits)


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

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=benjaminwagner@chromium.org

Change-Id: I7f933a6902fdd6e893e026b07b75a9b7843e3098
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1525803Reviewed-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@{#641126}
parent 418708c1
......@@ -133,7 +133,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': '61d38ade8c1d1b5d3793d1b983943099fc8ef6da',
'skia_revision': 'aefecad7c0d2c29c147a05ea385a2ad855cbbc20',
# 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