Commit 7203898e authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/angle eb0479e245f0..e54c3e3aa01c (1 commits)

https://chromium.googlesource.com/angle/angle.git/+log/eb0479e245f0..e54c3e3aa01c

git log eb0479e245f0..e54c3e3aa01c --date=short --no-merges --format='%ad %ae %s'
2019-08-09 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src b029d3697ea3..22ce39c8e1ec (5 commits)

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

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: I19bfff4d79cf5fcdbcc1b74c882ef774170e275e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746192Reviewed-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@{#685542}
parent 60d592d3
......@@ -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': 'eb0479e245f0b6ba5bbe00ef7299ecaa82f8c6e1',
'angle_revision': 'e54c3e3aa01cc5e1d0bbec28d6db619b22960bd3',
# 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