From 08a8de9f27f3e961d00698827115e9f61346efb1 Mon Sep 17 00:00:00 2001 From: sneak 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 one result line per package and, for a package that fails, everything its tests wrote, application log lines included. -race and the 90s per-package timeout are unchanged. Model: opus-5-5 --- script/test | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/script/test b/script/test index 301ae21..39bfcb7 100755 --- a/script/test +++ b/script/test @@ -27,6 +27,11 @@ # binaries build or run at once, each with at most eight parallel tests. Under # -race every test binary and every link costs a few hundred MB, so the # defaults (one per core) add up to several GB on a many-core host. +# +# 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 one result line per package and, for a package that fails, +# everything its tests wrote, application log lines included. set -eu ROOT="$(cd "$(dirname "$0")/.." && pwd -P)" @@ -34,7 +39,7 @@ ROOT="$(cd "$(dirname "$0")/.." && pwd -P)" main() { cd "$ROOT" "$ROOT/script/assets" - go test -v -race -p 4 -parallel 8 -timeout 90s ./... + go test -race -p 4 -parallel 8 -timeout 90s ./... } main "$@"