From: Charles Giessen <charles@lunarg.com>
Date: Tue, 3 Jan 2023 23:11:13 +0000 (-0700)
Subject: Fix allocation callback test to start at 0
X-Git-Tag: upstream/1.3.240~19
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a68ebff22ea8e7ec1843fc5db255cf69807a2aa9;p=platform%2Fupstream%2FVulkan-Loader.git

Fix allocation callback test to start at 0

While working on the code, it is common to start the allocation tests at a fail_index
greater than zero, usually close to when the issue starts. This was accidentally
checked in, this commit fixes that mistake.
---

diff --git a/tests/loader_alloc_callback_tests.cpp b/tests/loader_alloc_callback_tests.cpp
index 0f2f2d03..c7a4a1c4 100644
--- a/tests/loader_alloc_callback_tests.cpp
+++ b/tests/loader_alloc_callback_tests.cpp
@@ -440,7 +440,7 @@ TEST(Allocation, DriverEnvVarIntentionalAllocFail) {
     driver_files += (fs::path("totally_made_up") / "path_to_fake" / "jason_file.json").str();
     set_env_var("VK_DRIVER_FILES", driver_files);
     EnvVarCleaner cleaner("VK_DRIVER_FILES");
-    size_t fail_index = 66;  // 0
+    size_t fail_index = 0;
     VkResult result = VK_ERROR_OUT_OF_HOST_MEMORY;
     while (result == VK_ERROR_OUT_OF_HOST_MEMORY && fail_index <= 10000) {
         MemoryTracker tracker(MemoryTrackerSettings{false, 0, true, fail_index});