Commit 0419d91a authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/angle 73ec5b06ff9e..b8a27c5e6bb1 (1 commits)

https://chromium.googlesource.com/angle/angle.git/+log/73ec5b06ff9e..b8a27c5e6bb1

git log 73ec5b06ff9e..b8a27c5e6bb1 --date=short --no-merges --format='%ad %ae %s'
2019-08-05 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/glslang/src a0eb5efd2bad..3cea2e5882e3 (1 commits)

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

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

Bug: chromium:None
Change-Id: I351cf6e75d5e0593f6f97786b4e3f94af9454b1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1734761Reviewed-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@{#683969}
parent 79aa7407
......@@ -157,7 +157,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': '73ec5b06ff9ee23439c9029b99194dd1d5b4c267',
'angle_revision': 'b8a27c5e6bb16c050814f72f9c80ebbe023002c6',
# 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