commit 8a8668b4721097de657ad8b30d45f60f62433c6f
author Greg Daniel <egdaniel@google.com> Mon Oct 31 16:34:42 2016 -0400
committer Skia Commit-Bot <skia-commit-bot@chromium.org> Mon Oct 31 22:49:07 2016 +0000
tree 77bb4033cb295a8faafa61db27594a4990a45b56
parent 3c1b7db2432d136df0fc50c2e3ee0b3792b01dd6

Remove check of INITIALIZATION_FAILED in qcomm vulkan runs

This was another workaround for a flaky bug that happened on Adreno devices.
With all the devices updated to newer drivers I want to see if it still
happens. I haven't been able to repo the original bug locally with multiple
runs, so I think it is time to step it up to the bots.

BUG=skia:

GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=4212

Change-Id: Idc260785096b054cf0fb30ce9ff0d97178c10ed6
Reviewed-on: https://skia-review.googlesource.com/4212
Reviewed-by: Ben Wagner <benjaminwagner@google.com>
Commit-Queue: Greg Daniel <egdaniel@google.com>

src/gpu/vk/GrVkGpu.cpp

diff --git a/src/gpu/vk/GrVkGpu.cpp b/src/gpu/vk/GrVkGpu.cpp
index 7d75921..f7239d6 100644
--- a/src/gpu/vk/GrVkGpu.cpp
+++ b/src/gpu/vk/GrVkGpu.cpp
@@ -182,13 +182,7 @@
 #endif
 
 #ifdef SK_DEBUG
-    if (this->vkCaps().allowInitializationErrorOnTearDown()) {
-        SkASSERT(VK_SUCCESS == res ||
-                 VK_ERROR_DEVICE_LOST == res ||
-                 VK_ERROR_INITIALIZATION_FAILED == res);
-    } else {
-        SkASSERT(VK_SUCCESS == res || VK_ERROR_DEVICE_LOST == res);
-    }
+    SkASSERT(VK_SUCCESS == res || VK_ERROR_DEVICE_LOST == res);
 #endif
 
     fCopyManager.destroyResources(this);