Roll src/third_party/skia/ b3a695940..1804b3528 (4 commits)

https://skia.googlesource.com/skia.git/+log/b3a6959408e1..1804b3528c53

$ git log b3a695940..1804b3528 --date=short --no-merges --format='%ad %ae %s'
2018-04-19 csmartdalton ccpr: Don't preempt the convex path renderer
2018-04-19 benjaminwagner Add more angle_gl_* configs for NVIDIA.
2018-04-19 jvanverth Remove ambient clamp hack for analytic shadows.
2018-04-19 brianosman Remove duplicate predefined configs

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;luci.chromium.try:android_optional_gpu_tests_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
TBR=scroggo@chromium.org

Change-Id: I3d877b212203de9c14d4c98067dc90ee5c7abdff
Reviewed-on: https://chromium-review.googlesource.com/1020442Reviewed-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@{#552240}
parent 5db462e7
......@@ -89,7 +89,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': 'b3a6959408e177bc38b96cb29cfac692f876e100',
'skia_revision': '1804b3528c53f52664d9d344950f38e62bf7a71f',
# 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