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

Roll src/third_party/angle a96b79f90940..d7e0a36ac618 (1 commits)

https://chromium.googlesource.com/angle/angle.git/+log/a96b79f90940..d7e0a36ac618


git log a96b79f90940..d7e0a36ac618 --date=short --no-merges --format='%ad %ae %s'
2019-07-29 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src f54b8653dd9d..9559cdbdf011 (1 commits)


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

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=geofflang@google.com

Bug: chromium:None
Change-Id: I7a9e5eef47c20950397751d69e3f3b8040620f55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723837Reviewed-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@{#681745}
parent c893c5aa
......@@ -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': 'a96b79f909403b53ea4c577912bdf611da9ff064',
'angle_revision': 'd7e0a36ac6182c56f442e73d49a2d532dfa01680',
# 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