chore: remove unused `LOCK_TIME` constant
What the developer wrote
Authored by Roman Zeyde
chore: remove unused `LOCK_TIME` constant
[no changelog]
What changed, and why it matters
This commit simply deletes an unused constant named LOCK_TIME from a test configuration file. It does not change any device firmware, wallet logic, or security behavior. There is no security issue here.
No action needed. This is a routine cleanup commit with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff removes the line LOCK_TIME = 0.2 from tests/conftest.py. The constant is not referenced anywhere in the changed file or in any visible code, and the file is part of the test suite, not the firmware runtime. No functional code is modified.
Changed components
tests/conftest.pyInspect captured patch +0 / −2
diff --git a/tests/conftest.py b/tests/conftest.py
index 0fd9a8be..6594e5a7 100644
--- a/tests/conftest.py
+++ b/tests/conftest.py
@@ -60,8 +60,6 @@ CORE = HERE.parent / "core"
LOG = logging.getLogger(__name__)
-LOCK_TIME = 0.2
-
# So that we see details of failed asserts from this module
pytest.register_assert_rewrite("tests.common")
pytest.register_assert_rewrite("tests.input_flows")
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.