Do not report warning if OOM testing is incomplete
authorPyry Haulos <phaulos@google.com>
Mon, 8 May 2017 16:15:25 +0000 (09:15 -0700)
committerPyry Haulos <phaulos@google.com>
Fri, 12 May 2017 17:18:37 +0000 (13:18 -0400)
commit0807669bba13bf742b2df4774bb0054fa6b6e844
tree6b96f7e13d4cd9ef5dadc4cdf8dc2521260d6e9a
parenta11c1a38ff00f6274e58d8d2476d0cc0de57cb2d
Do not report warning if OOM testing is incomplete

object_management.alloc_callback_fail tests are trying to exhaustively
test all OOM paths in vkCreate* functions. However, to keep test run-
time reasonable, they have a fixed maximum allocation count and if
that is exceeded report a warning since OOM testing was not
exhaustive.

Since an implementation that requires more allocations than the limit
is valid, this commit changes the tests to report clean Pass instead
of CompatibilityWarning. Note about incomplete OOM testing is included
in the test log contents instead.

Affects:

dEQP-VK.api.object_management.alloc_callback_fail.*

VK-GL-CTS issue: 399
Components: Vulkan

Change-Id: I6890321546ae42f2646b8653007172d4b8affb8a
external/vulkancts/modules/vulkan/api/vktApiObjectManagementTests.cpp