test(core): use 10s timeout for `make test_emu_sanity`
What the developer wrote
Authored by Roman Zeyde
test(core): use 10s timeout for `make test_emu_sanity`
[no changelog]
What changed, and why it matters
This commit only changes a test command in the build Makefile. It wraps an emulator sanity check with a 10-second timeout so automated tests don't hang indefinitely if the emulator fails to start. There is no change to firmware code, cryptography, device behavior, or anything users interact with.
No security action needed. This is a benign test-infrastructure quality-of-life change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies core/Makefile, adding timeout -v 10 in front of the test_emu_sanity target. This target runs the Trezor emulator with --command true to verify it starts without crashing. The timeout is a CI/test-harness hardening measure to prevent runaway jobs. No source code, firmware binary, or security boundary is affected.
Changed components
core/MakefileInspect captured patch +1 / −1
diff --git a/core/Makefile b/core/Makefile
index a364993c4..bed0da445 100644
--- a/core/Makefile
+++ b/core/Makefile
@@ -186,7 +186,7 @@ test_rust: ## run rs unit tests
-- --test-threads=1 --nocapture
test_emu_sanity: ## make sure the emulator doesn't crash on startup
- $(EMU) --disable-animation --headless --temporary-profile --command true
+ timeout -v 10 $(EMU) --disable-animation --headless --temporary-profile --command true
test_emu: ## run selected device tests from python-trezor
$(EMU_TEST) $(PYTEST) $(TESTPATH)/device_tests $(TESTOPTS) --lang=$(TEST_LANG)
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.