Consider rounding mode differences in mipmap tests
authorTony Wasserka <tony.wasserka@imgtec.com>
Tue, 3 Apr 2018 14:40:21 +0000 (15:40 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Tue, 18 Sep 2018 07:22:15 +0000 (03:22 -0400)
commite79d57ad2cf57653853dacad63316d3823d8df8c
tree875709f575901da885e3bf70a97bf0c37edb92a6
parent16b82e759f3e60493d6fd016b7c8beb8ae30b28a
Consider rounding mode differences in mipmap tests

The tests already tolerate a threshold for rounding mode differences
for the result of a downscaling vkCmdBlitImage, however the accumulated
difference between Round-To-Nearest and Round-To-Zero may exceed the
current threshold. With this change, the expected result is generated
from the preceding device-rendered mipmap instead, so any legitimate
error will always be within the threshold now.

Affects:

dEQP-VK.api.copy_and_blit.core.blit_image.all_formats.generate_mipmaps.*_linear

Components: Vulkan

VK-GL-CTS issue: 1106

Change-Id: I0999419320d1b2384f42fbc8eddda29e79147bd4
(cherry picked from commit b861ca1e6d4c002d4359a71dbff1cdf898e79aca)
external/vulkancts/modules/vulkan/api/vktApiCopiesAndBlittingTests.cpp