main side of 414: cheaper test hashing, and failing tests visible in the build log (closes #414)

Conversation 3 Commits 2 Files Changed 5

+79 -3

2 Commits

Author	SHA1	Message	Date
sneak	d871bf2d6c	Run the test suite without -v so a failure shows in the build log (closes #414 ) check / check (push) Waiting to run Details 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	2026-10-02 04:01:58 +00:00
clawbot	68759dc8e1	Keep make test under 2 GB of memory (closes #344 ) Every test that starts a database seeds the admin account, hashing its password with Argon2id at 64 MB, about 150 MB under -race, and internal/handlers and internal/database ran dozens of those at once. That was the memory, and most of internal/handlers' run time; the product code does not leak. HashPassword now hashes at a 1 MB cost only when testing.Testing() reports a test binary, so every test package gets it with nothing to add and a binary built by go build always hashes at the shipped parameters. TestHashPassword_ShippedParameters still hashes and verifies through HashPassword at the shipped cost. script/test adds -p 4 -parallel 8. Model: opus-5-5	2026-10-02 01:58:36 +00:00

Author

SHA1

Message

Date

sneak

d871bf2d6c

Run the test suite without -v so a failure shows in the build log (closes #414 )

check / check (push) Waiting to run

Details

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

2026-10-02 04:01:58 +00:00

clawbot

68759dc8e1

Keep make test under 2 GB of memory (closes #344 )

Every test that starts a database seeds the admin account, hashing its password with Argon2id at 64 MB, about 150 MB under -race, and internal/handlers and internal/database ran dozens of those at once. That was the memory, and most of internal/handlers' run time; the product code does not leak.

HashPassword now hashes at a 1 MB cost only when testing.Testing() reports a test binary, so every test package gets it with nothing to add and a binary built by go build always hashes at the shipped parameters. TestHashPassword_ShippedParameters still hashes and verifies through HashPassword at the shipped cost. script/test adds -p 4 -parallel 8.

Model: opus-5-5

2026-10-02 01:58:36 +00:00

main side of 414: cheaper test hashing, and failing tests visible in the build log (closes #414) #416