Commit df3cc205 by angle-autoroll Committed by Commit Bot

Roll third_party/vulkan-tools/src bb32b2a70168..ae6787114fb5 (4 commits)

https://chromium.googlesource.com/external/github.com/KhronosGroup/Vulkan-Tools.git/+log/bb32b2a70168..ae6787114fb5 git log bb32b2a70168..ae6787114fb5 --date=short --first-parent --format='%ad %ae %s' 2020-04-09 tobine@google.com mockicd: Track memory allocation size 2020-04-09 petr_kraus@email.cz icd: Make swapchain images persistent 2020-04-09 petr_kraus@email.cz icd: Fix vkGetSwapchainImages behavior 2020-04-09 petr_kraus@email.cz icd: Fix vkAcquireNextImageKHR generation Created with: gclient setdep -r third_party/vulkan-tools/src@ae6787114fb5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/vulkan-tools-angle-autoroll Please CC jonahr@google.com,tobine@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: jonahr@google.com,tobine@google.com Change-Id: I284c0d5d29fa5c43ba82b6f2d1b901d188f28637 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2144983Reviewed-by: 's avatarangle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
parent 405f8e7b
......@@ -55,7 +55,7 @@ vars = {
'vulkan_loader_revision': 'bb8be13e3ffeb27a95858941c62243a59c1f0944',
# Current revision of Khronos Vulkan-Tools.
'vulkan_tools_revision': 'bb32b2a7016893617453ff9a3dba2a7a17c57b9b',
'vulkan_tools_revision': 'ae6787114fb59b76d37b6d8d64752b98bd01ff03',
# Current revision of Khronos Vulkan-ValidationLayers.
'vulkan_validation_revision': '47d5e27460afef3b3cee108317de06b70d70fd19',
......
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