ci: increase the time allowance for v2 selfcheck
What the developer wrote
Authored by Jon Griffiths
ci: increase the time allowance for v2 selfcheck
This is likely caused by increased stack checks; increasing the speed of
individual RPC calls will be made in the future on a case by case basis.
What changed, and why it matters
This commit simply loosens a test timeout in the project's automated test suite. It changes how long a self-check test is allowed to take, likely because the test was failing due to slower internal safety checks. There is no change to the actual device firmware or wallet security logic, and no security issue is introduced.
No action needed. This is a benign CI/test-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies test_jade.py to increase the allowed duration for the v2 remote selfcheck from 46,000 ms to 52,000 ms on S3 hardware. The change is purely in test assertion thresholds and does not touch firmware, RPC handling, cryptography, or any runtime security boundary. The commit message attributes the need for more time to increased stack checks.
Changed components
test_jade.py automated test suiteInspect captured patch +1 / −1
diff --git a/test_jade.py b/test_jade.py
index 50f90ff..58fd9b3 100644
--- a/test_jade.py
+++ b/test_jade.py
@@ -3884,7 +3884,7 @@ def run_interface_tests(jadeapi,
if not isble:
time_ms = jadeapi.run_remote_selfcheck()
logger.info(f'selfcheck time: {time_ms} ms')
- assert qemu or time_ms < (46000 if is_s3 else 132000)
+ assert qemu or time_ms < (52000 if is_s3 else 132000)
# Test good pinserver handshake, and also 'bad sig' pinserver
test_handshake(jadeapi.jade)
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.