Top priority: this comes before all other work in this repo. Owner's words (sneak/project-management#20): "main and next should be green on all managed repos at all times. any divergence is a top priority."
Red: main (f703b72c) and next (1cafaeb9). script/cibuild fails at RUN make test in the Dockerfile: make test exits 1, and every package that shows a result passed. The failing test cannot be seen: script/test always runs go test -v, and the step's output passes the 2 MiB log limit of the Docker build, which cuts it off before the failure. internal/handlers is the package with no result line in either run. The host was busy (three builds at once), which #225 says makes the internal/handlers tests fail.
Reproduce: clone the branch fresh and run script/cibuild, with other builds running at the same time.
Related causes already filed: #225 (tests fail under host load), #198 (make test too slow, mostly internal/handlers), #315 (script/test always verbose), #344 (make test needs up to 6.7 GiB of RAM).
Definition of done:
A failing test is visible in the script/cibuild output.
The cause is fixed for real: no test skipped, deleted or retried into passing, no check weakened.
next: through a reviewed PR to next, a fresh clone's script/cibuild passes several times in a row, including while other builds run.
main: the same fix, and nothing else from next, lands on main through its own reviewed PR targeting main, then main passes the same way.
Model: opus-5-5
Top priority: this comes before all other work in this repo. Owner's words (https://git.eeqj.de/sneak/project-management/issues/20): "main and next should be green on all managed repos at all times. any divergence is a top priority."
Red: `main` (`f703b72c`) and `next` (`1cafaeb9`). `script/cibuild` fails at `RUN make test` in the `Dockerfile`: `make test` exits 1, and every package that shows a result passed. The failing test cannot be seen: `script/test` always runs `go test -v`, and the step's output passes the 2 MiB log limit of the Docker build, which cuts it off before the failure. `internal/handlers` is the package with no result line in either run. The host was busy (three builds at once), which https://git.eeqj.de/sneak/webhooker/issues/225 says makes the `internal/handlers` tests fail.
Reproduce: clone the branch fresh and run `script/cibuild`, with other builds running at the same time.
Related causes already filed: https://git.eeqj.de/sneak/webhooker/issues/225 (tests fail under host load), https://git.eeqj.de/sneak/webhooker/issues/198 (`make test` too slow, mostly `internal/handlers`), https://git.eeqj.de/sneak/webhooker/issues/315 (`script/test` always verbose), https://git.eeqj.de/sneak/webhooker/issues/344 (`make test` needs up to 6.7 GiB of RAM).
Definition of done:
- A failing test is visible in the `script/cibuild` output.
- The cause is fixed for real: no test skipped, deleted or retried into passing, no check weakened.
- `next`: through a reviewed PR to `next`, a fresh clone's `script/cibuild` passes several times in a row, including while other builds run.
- `main`: the same fix, and nothing else from `next`, lands on `main` through its own reviewed PR targeting `main`, then `main` passes the same way.
Model: opus-5-5
clawbot
self-assigned this 2026-10-02 02:26:36 +02:00
Reading: internal/handlers never prints a result line because under host load the package overruns go test's 90-second timeout. Its tests hash the admin password with Argon2id at 64 MB on every database start, many at once under -race, which is also what #344 measures. The failure itself is hidden because script/test runs go test -v, whose output passes the Docker build's 2 MiB log limit first.
next:#404 (test-only hashing cost, bounded test parallelism) is the fix for the cause and lands first; it is under review now. This issue's PR to next then makes script/test run without -v, so only failures and per-package results reach the log, and proves the result: a fresh clone's script/cibuild passing several times in a row while other builds run. If the handlers package still fails with 404 in place, that failure is found and fixed in this PR; nothing is skipped, retried or given a longer timeout.
main: a branch off main carrying exactly those two changes and nothing else from next, in its own PR targeting main, independently reviewed, then proven the same way.
Model: opus-5-5
Plan.
Reading: `internal/handlers` never prints a result line because under host load the package overruns `go test`'s 90-second timeout. Its tests hash the admin password with Argon2id at 64 MB on every database start, many at once under `-race`, which is also what https://git.eeqj.de/sneak/webhooker/issues/344 measures. The failure itself is hidden because `script/test` runs `go test -v`, whose output passes the Docker build's 2 MiB log limit first.
- **`next`:** https://git.eeqj.de/sneak/webhooker/pulls/404 (test-only hashing cost, bounded test parallelism) is the fix for the cause and lands first; it is under review now. This issue's PR to `next` then makes `script/test` run without `-v`, so only failures and per-package results reach the log, and proves the result: a fresh clone's `script/cibuild` passing several times in a row while other builds run. If the handlers package still fails with 404 in place, that failure is found and fixed in this PR; nothing is skipped, retried or given a longer timeout.
- **`main`:** a branch off `main` carrying exactly those two changes and nothing else from `next`, in its own PR targeting `main`, independently reviewed, then proven the same way.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Top priority: this comes before all other work in this repo. Owner's words (sneak/project-management#20): "main and next should be green on all managed repos at all times. any divergence is a top priority."
Red:
main(f703b72c) andnext(1cafaeb9).script/cibuildfails atRUN make testin theDockerfile:make testexits 1, and every package that shows a result passed. The failing test cannot be seen:script/testalways runsgo test -v, and the step's output passes the 2 MiB log limit of the Docker build, which cuts it off before the failure.internal/handlersis the package with no result line in either run. The host was busy (three builds at once), which #225 says makes theinternal/handlerstests fail.Reproduce: clone the branch fresh and run
script/cibuild, with other builds running at the same time.Related causes already filed: #225 (tests fail under host load), #198 (
make testtoo slow, mostlyinternal/handlers), #315 (script/testalways verbose), #344 (make testneeds up to 6.7 GiB of RAM).Definition of done:
script/cibuildoutput.next: through a reviewed PR tonext, a fresh clone'sscript/cibuildpasses several times in a row, including while other builds run.main: the same fix, and nothing else fromnext, lands onmainthrough its own reviewed PR targetingmain, thenmainpasses the same way.Model: opus-5-5
Plan.
Reading:
internal/handlersnever prints a result line because under host load the package overrunsgo test's 90-second timeout. Its tests hash the admin password with Argon2id at 64 MB on every database start, many at once under-race, which is also what #344 measures. The failure itself is hidden becausescript/testrunsgo test -v, whose output passes the Docker build's 2 MiB log limit first.next: #404 (test-only hashing cost, bounded test parallelism) is the fix for the cause and lands first; it is under review now. This issue's PR tonextthen makesscript/testrun without-v, so only failures and per-package results reach the log, and proves the result: a fresh clone'sscript/cibuildpassing several times in a row while other builds run. If the handlers package still fails with 404 in place, that failure is found and fixed in this PR; nothing is skipped, retried or given a longer timeout.main: a branch offmaincarrying exactly those two changes and nothing else fromnext, in its own PR targetingmain, independently reviewed, then proven the same way.Model: opus-5-5