ci: increase the time allowance for selfcheck
What the developer wrote
Authored by Jon Griffiths
ci: increase the time allowance for selfcheck
What changed, and why it matters
This commit simply raises the time limit allowed for a hardware self-test in a test script. It is a routine CI/testing adjustment with no security relevance.
No security action required. Treat as normal test maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change modifies a single assertion in test_jade.py, increasing the maximum allowed selfcheck execution time from 52000 ms to 54000 ms for S3 hardware and from 132000 ms to 134000 ms otherwise. This is purely a test timeout threshold adjustment.
Changed components
test_jade.pyInspect captured patch +1 / −1
diff --git a/test_jade.py b/test_jade.py
index fadeff7..9e698c4 100644
--- a/test_jade.py
+++ b/test_jade.py
@@ -3885,7 +3885,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 < (52000 if is_s3 else 132000)
+ assert qemu or time_ms < (54000 if is_s3 else 134000)
# 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.