Justify the handlers tests' start limit with a measurement (closes #225) #432

Merged
clawbot merged 1 commits from issue-225-handlers-test-timing into next 2026-10-02 14:08:55 +02:00
1 Commits
Author SHA1 Message Date
clawbot 28dd1f326e Justify the handlers tests' start limit with a measurement (closes #225)
check / check (push) Waiting to run
The cost that pushed internal/handlers near its 90s package timeout, and test app starts past fx's 15s start timeout, was every start hashing the admin password at 64 MB; that went with #404. Measured since under the host's real load, the package takes 8.5s and the slowest test app start 0.49s, so neither limit changes. newTestApp now says what its start limit catches and the measurement behind it, and script/test notes that its figures predate that change and gives the current ones. No test changes what it asserts.

Model: opus-5-5
2026-10-02 11:46:05 +00:00