Commit 6c0b5de0 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/angle 6d9b8908b0bb..0a56f0e3d22d (2 commits)

https://chromium.googlesource.com/angle/angle.git/+log/6d9b8908b0bb..0a56f0e3d22d


git log 6d9b8908b0bb..0a56f0e3d22d --date=short --no-merges --format='%ad %ae %s'
2019-05-30 timvp@google.com Vulkan: Update front face mode during syncState()
2019-05-30 cnorthrop@google.com Revert "Vulkan: Use atomics in SerialFactory."


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

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

Change-Id: I8b441387e8e0b60d8038598ed3a5db8bd6565a1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637500Reviewed-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@{#664834}
parent 809f4921
......@@ -150,7 +150,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': '6d9b8908b0bb1c2a71544cbaad5c5a3f8ee07ddf',
'angle_revision': '0a56f0e3d22dad426f0f97e499d70c063983f4b7',
# 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