From 1316dbc65bc5ea6cafc3923498795e8e6746d601 Mon Sep 17 00:00:00 2001 From: baldurk Date: Thu, 16 Jul 2020 17:17:53 +0100 Subject: [PATCH] When iterating captures, don't compare outputs that are uninitialised --- util/test/tests/Iter_Test.py | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/util/test/tests/Iter_Test.py b/util/test/tests/Iter_Test.py index 2a416541d..5061f3a54 100644 --- a/util/test/tests/Iter_Test.py +++ b/util/test/tests/Iter_Test.py @@ -140,6 +140,11 @@ class Iter_Test(rdtest.TestCase): else: debugged = value.value.fv[0:value.columns] + # For now, ignore debugged values that are uninitialised. This is an application bug but it causes false reports of problems + for idx in range(4): + if value.value.uv[idx] == 0xcccccccc: + debugged[idx] = expect[idx] + # Unfortunately we can't ever trust that we should get back a matching results, because some shaders # rely on undefined/inaccurate maths that we don't emulate. # So the best we can do is log an error for manual verification @@ -268,6 +273,11 @@ class Iter_Test(rdtest.TestCase): debuggedValue = [debugged.value.f.x, debugged.value.f.y, debugged.value.f.z, debugged.value.f.w] + # For now, ignore debugged values that are uninitialised. This is an application bug but it causes false reports of problems + for idx in range(4): + if debugged.value.uv[idx] == 0xcccccccc: + debuggedValue[idx] = lastmod.shaderOut.col.floatValue[idx] + # Unfortunately we can't ever trust that we should get back a matching results, because some shaders # rely on undefined/inaccurate maths that we don't emulate. # So the best we can do is log an error for manual verification