What the developer wrote
Authored by Niklas Dusenlund
chore: Less verbose rust unit tests
Only output stdout/err of unit tests in case a verbose build was
requested.
What changed, and why it matters
This commit only changes how much output is shown when running Rust unit tests during firmware builds. It makes the tests less chatty unless verbose mode is explicitly requested. There is no security relevance.
No security action needed. This is a routine developer-experience change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch replaces the unconditional --nocapture argument passed to Rust unit tests with a CMake generator expression that only adds --no-capture when CMAKE_VERBOSE_MAKEFILE is enabled. This is a build-system/UX change affecting test output verbosity only.
Changed components
src/CMakeLists.txtInspect captured patch +1 / −1
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index c50128d..7ebbd07 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -278,7 +278,7 @@ if(NOT CMAKE_CROSSCOMPILING)
--manifest-path ${CMAKE_CURRENT_SOURCE_DIR}/rust/Cargo.toml
--target-dir ${RUST_BINARY_DIR}/all-features
--
- --nocapture
+ $<$<BOOL:${CMAKE_VERBOSE_MAKEFILE}>:--no-capture>
--test-threads 1
WORKING_DIRECTORY
${CMAKE_CURRENT_SOURCE_DIR}/rust
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.