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

Roll src/third_party/angle 3c6b2e1613c8..39e2669a3e92 (1 commits)

https://chromium.googlesource.com/angle/angle.git/+log/3c6b2e1613c8..39e2669a3e92

git log 3c6b2e1613c8..39e2669a3e92 --date=short --no-merges --format='%ad %ae %s'
2019-08-26 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src aef8f92b2bb6..1eb89172a82b (3 commits)

Created with:
  gclient setdep -r src/third_party/angle@39e2669a3e92

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

Bug: chromium:None
Change-Id: I3d8a9b3f7c68e5557dac6ad22487f9efb0affce7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771291Reviewed-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@{#690316}
parent 233d52c5
......@@ -172,7 +172,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': '3c6b2e1613c844f7265895de5611c0528641d501',
'angle_revision': '39e2669a3e920a776b0c99335aa5f54826fac66f',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling SwiftShader
# 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