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

Roll src/third_party/skia ee90eb42fe4f..3349fb0195ff (1 commits)

https://skia.googlesource.com/skia.git/+log/ee90eb42fe4f..3349fb0195ff


git log ee90eb42fe4f..3349fb0195ff --date=short --no-merges --format='%ad %ae %s'
2019-04-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).


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

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

Change-Id: Ibea7b3847ec17d9c1a35777e6acbba5df2ab8e61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586341Reviewed-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@{#654619}
parent 29061a59
......@@ -129,7 +129,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': 'ee90eb42fe4ff3c740da1747c37fcf1479108ac5',
'skia_revision': '3349fb0195ff80db6cf6c14a5ce9aa4ea0340d0d',
# 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