ci(core): increase pytest timeout for T3W1 device tests
What changed, and why it matters
This commit only changes a CI test timeout setting in a GitHub Actions workflow. It increases how long automated tests for one Trezor device model (T3W1) are allowed to run before being cancelled. There is no change to firmware code, cryptography, user-facing behavior, or anything an attacker could exploit.
No security action needed. This is a benign CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/core.yml, raising the pytest session-timeout from 1800s (30m) to 2400s (40m) for the T3W1 model matrix job, and the GitHub Actions job timeout from 40 to 50 minutes. This is a pure CI/infrastructure tuning change with no product code modifications.
Changed components
.github/workflows/core.ymlInspect captured patch +2 / −2
diff --git a/.github/workflows/core.yml b/.github/workflows/core.yml
index 7f0cf152..38de5b78 100644
--- a/.github/workflows/core.yml
+++ b/.github/workflows/core.yml
@@ -288,8 +288,8 @@ jobs:
PYTEST_TIMEOUT: ${{ matrix.asan == 'asan' && 600 || 400 }}
ACTIONS_DO_UI_TEST: ${{ matrix.coins == 'universal' && matrix.asan == 'noasan' }}
TEST_LANG: ${{ matrix.lang }}
- TESTOPTS: "--durations 10 --session-timeout 1800" # 30m pytest global timeout
- timeout-minutes: 40
+ TESTOPTS: "--durations 10 --session-timeout ${{ matrix.model == 'T3W1' && '2400' || '1800' }}" # pytest global timeout
+ timeout-minutes: 50 # CI job timeout
steps:
- uses: actions/checkout@v4
with:
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.