From b540f631ab64d95d86d20ad2f2cef038efea0fd2 Mon Sep 17 00:00:00 2001
From: baldurk <baldurk@baldurk.org>
Date: Tue, 21 Jul 2020 12:42:09 +0100
Subject: [PATCH] Don't overwrite idx variable with loop iterator

---
 util/test/tests/Iter_Test.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/util/test/tests/Iter_Test.py b/util/test/tests/Iter_Test.py
index 5061f3a54..4bf228d43 100644
--- a/util/test/tests/Iter_Test.py
+++ b/util/test/tests/Iter_Test.py
@@ -141,9 +141,9 @@ class Iter_Test(rdtest.TestCase):
                     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]
+                for comp in range(4):
+                    if value.value.uv[comp] == 0xcccccccc:
+                        debugged[comp] = expect[comp]
 
                 # 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.