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

Roll src/third_party/angle bbdeee914aeb..48bbc53ea4d0 (2 commits)

https://chromium.googlesource.com/angle/angle.git/+log/bbdeee914aeb..48bbc53ea4d0


git log bbdeee914aeb..48bbc53ea4d0 --date=short --no-merges --format='%ad %ae %s'
2019-01-02 bryan.bernhart@intel.com ES31: Fix for reading back initialized SSBO buffers in D3D11
2019-01-02 syoussefi@chromium.org Suppress flaky Linux/Intel/OpenGL test.


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

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

Change-Id: Ib4f6846d4ee3b65da1681f8d06641b1eb756533f
Reviewed-on: https://chromium-review.googlesource.com/c/1393356Reviewed-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@{#619535}
parent fa268a7a
......@@ -133,7 +133,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': 'bbdeee914aeb1fa5f6a2ea65b31c879c8af10b30',
'angle_revision': '48bbc53ea4d04920093ca44344abcf6edc2f0d2d',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling build tools
# 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