diff options
| author | Charles Giessen <charles@lunarg.com> | 2023-01-03 16:11:13 -0700 |
|---|---|---|
| committer | Charles Giessen <46324611+charles-lunarg@users.noreply.github.com> | 2023-01-09 12:04:34 -0700 |
| commit | a68ebff22ea8e7ec1843fc5db255cf69807a2aa9 (patch) | |
| tree | 63beaf77fa13845e35df0d385e15319b29c780b8 | |
| parent | 431f1af98a7ccfc03e98979629b55f50e18d6a10 (diff) | |
| download | Vulkan-Loader-a68ebff22ea8e7ec1843fc5db255cf69807a2aa9.tar.gz Vulkan-Loader-a68ebff22ea8e7ec1843fc5db255cf69807a2aa9.tar.bz2 Vulkan-Loader-a68ebff22ea8e7ec1843fc5db255cf69807a2aa9.zip | |
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.
| -rw-r--r-- | tests/loader_alloc_callback_tests.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
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}); |