Limit call of getQueryPoolResults to BUILD_TYPE_DEVICE
authorNeslisah <Neslisah.Torosdagli@amd.com>
Mon, 26 Sep 2022 20:00:49 +0000 (16:00 -0400)
committerMatthew Netsch <quic_mnetsch@quicinc.com>
Fri, 7 Oct 2022 22:15:22 +0000 (22:15 +0000)
commitb5b6f13a8be602ce56397e85638eba80cdfc141d
tree4335d40bbd8f3c5e238ce72def4bdf728d2cefd2
parentacb1986d279c53ff7478a542296f4cdf9d1d1a77
Limit call of getQueryPoolResults to BUILD_TYPE_DEVICE

When the buildType is BUILD_TYPE_HOST, queryPool results are retrieved immediately to the CPU, and queryPool is not set to the result value.
Due to unset value at queryPool, later calling getQueryPoolResults causes the size to be messed up, and assertion to be trigerred.
The intention to call getQueryPoolResults is for BUILD_TYPE_DEVICE where you need to wait for cmdBuffer to be executed.
Call of getQueryPoolResults should only be made if the build type is BUILD_TYPE_DEVICE.

Affects:
dEQP-VK.ray_tracing_pipeline.acceleration_structures.copy_within_pipeline.cpu.*

Components: Vulkan

https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/4016

Change-Id: I2e8c3dc9c56c98c288bba17d6c4074a9b88e0851
external/vulkancts/modules/vulkan/ray_tracing/vktRayTracingAccelerationStructuresTests.cpp