ci(core): increase individual test timeout for upgrade tests
What changed, and why it matters
This commit only increases a test timeout value in a GitHub Actions CI workflow from 60 to 70 seconds. It does not change any firmware code, cryptographic logic, or user-facing behavior. There is no security relevance.
No security action needed. Treat as routine CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change modifies .github/workflows/core.yml, raising the PYTEST_TIMEOUT environment variable for upgrade tests from 60 to 70 seconds. It is a pure CI configuration tweak with no impact on the Trezor firmware runtime, device interfaces, or security boundaries.
Changed components
GitHub Actions CI workflow for core firmware upgrade testsInspect captured patch +1 / −1
diff --git a/.github/workflows/core.yml b/.github/workflows/core.yml
index 86b4f488..1f2547eb 100644
--- a/.github/workflows/core.yml
+++ b/.github/workflows/core.yml
@@ -417,7 +417,7 @@ jobs:
model: [T2T1, T3W1]
asan: ${{ fromJSON(needs.param.outputs.asan) }}
env:
- PYTEST_TIMEOUT: 60
+ PYTEST_TIMEOUT: 70
TESTOPTS: "--durations 10"
timeout-minutes: 20
steps:
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.