From 540ef5d621fe453c6a3b6a8935b929d9a85baa8c Mon Sep 17 00:00:00 2001
From: sneak <sneak@sneak.berlin>
Date: Fri, 2 Oct 2026 00:32:25 +0000
Subject: [PATCH] Run the test suite without -v so a failure shows in the build
 log (closes #414)

The Docker build cuts each step's log off at 2 MiB. script/test ran
go test -v, whose output for the whole suite passed that limit before
any failure was printed, so a red build showed no failing test. Without
-v, go test prints only the output of failing tests and one result
line per package. -race and the 90s per-package timeout are unchanged.

Model: opus-5-5
---
 script/test | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/script/test b/script/test
index 44f0308..457e293 100755
--- a/script/test
+++ b/script/test
@@ -22,6 +22,10 @@
 # The one figure above 90s is GOMAXPROCS 1, a synthetic core floor rather than
 # a condition CI runs under. If a CPU-limited runner ever puts a real run near
 # 67s, that is the datum to revisit the org figure with.
+#
+# No -v: the Docker build cuts each step's log off at 2 MiB, and verbose output
+# from the whole suite passes that before a failure is printed. Without it, go
+# test prints only the output of failing tests and one result line per package.
 set -eu
 
 ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
@@ -29,7 +33,7 @@ ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
 main() {
     cd "$ROOT"
     "$ROOT/script/assets"
-    go test -v -race -timeout 90s ./...
+    go test -race -timeout 90s ./...
 }
 
 main "$@"