Roll src/third_party/skia/ 296de50b4..e027e1947 (4 commits)

https://skia.googlesource.com/skia.git/+log/296de50b4c2e..e027e19477f8

$ git log 296de50b4..e027e1947 --date=short --no-merges --format='%ad %ae %s'
2018-03-13 benjaminwagner Temporarily remove Win10 QuadroP400 from CQ.
2018-03-13 caryclark consolidate SaveLayerFlag internal references
2018-03-13 rmistry Increase Android framework bot deadline since we are now building more
2018-03-13 bungeman Include correct trace.h.

Created with:
  roll-dep src/third_party/skia


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

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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=stephana@chromium.org

Change-Id: Ia9ed064a7e3601d6bac67719c2630cd82010c7a9
Reviewed-on: https://chromium-review.googlesource.com/961266Reviewed-by: default avatarskia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542932}
parent bd1e4485
......@@ -79,7 +79,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': '296de50b4c2e31f94b8c3fafae8fcd7bcfb00e0b',
'skia_revision': 'e027e19477f8ad10ae3f26ea996c1bff350d89f3',
# 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