Add newline to fuzz log statements
What the developer wrote
Authored by Wilmer Paulino
Add newline to fuzz log statements
This regressed at some point, making the logs harder to parse on a
failed test run.
What changed, and why it matters
This commit fixes a formatting issue in fuzz testing logs by adding a missing newline at the end of each log entry. It only affects test output readability and has no security relevance.
No security action needed. Treat as a normal code-quality/test-output fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change replaces write! with writeln! in TestLogger::log within the fuzz test utility. This restores newline-terminated log lines that had regressed, making fuzz test failure logs easier to parse. The code is in a fuzzing test helper and does not alter production logic, cryptography, networking, or state handling.
Changed components
fuzz/src/utils/test_logger.rsInspect captured patch +1 / −1
diff --git a/fuzz/src/utils/test_logger.rs b/fuzz/src/utils/test_logger.rs
index f836987..8f38d08 100644
--- a/fuzz/src/utils/test_logger.rs
+++ b/fuzz/src/utils/test_logger.rs
@@ -59,6 +59,6 @@ impl<'a, Out: Output> Write for LockedWriteAdapter<'a, Out> {
impl<Out: Output> Logger for TestLogger<Out> {
fn log(&self, record: Record) {
- write!(LockedWriteAdapter(&self.out), "{:<6} {}", self.id, record).unwrap();
+ writeln!(LockedWriteAdapter(&self.out), "{:<6} {}", self.id, record).unwrap();
}
}
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.