Commit 2268cef2 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/angle 193a284d34d2..5ca3e5a0b285 (2 commits)

https://chromium.googlesource.com/angle/angle.git/+log/193a284d34d2..5ca3e5a0b285


git log 193a284d34d2..5ca3e5a0b285 --date=short --no-merges --format='%ad %ae %s'
2018-10-31 ynovikov@chromium.org Fix ShaderStorageBlockOutputHLSL::writeEOpIndexDirectOrIndirectOutput
2018-10-31 jiajia.qin@intel.com ES31: add row major matrix support (part 1)


Created with:
  gclient setdep -r src/third_party/angle@5ca3e5a0b285

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: I48a7edc3a87fe4fcb57c313d56b4d38d79de4800
Reviewed-on: https://chromium-review.googlesource.com/c/1310553Reviewed-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@{#604345}
parent 500106c1
......@@ -123,7 +123,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling ANGLE
# and whatever else without interference from each other.
'angle_revision': '193a284d34d268cb106da5e7a697a66f8880cd37',
'angle_revision': '5ca3e5a0b285cbd2a4ba77a1082d62cf0cbea9fb',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling build tools
# 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