bug: TestBoundedLoad_OldestLoadedSet hangs (pre-existing)

[Kpa-clawbot]

Context

Multiple reviewers flagged in PR #1735 (round-1 review) that TestBoundedLoad_OldestLoadedSet hangs in CI / local test runs. It pre-dates the #1724 work (the PR's tests deliberately skip it via -skip TestBoundedLoad).

Proposal

Reproduce locally, identify the hang condition, fix or quarantine with t.Skip + a code comment pointing back to this issue.

Notes

Hang is reliable enough that the local test run for PR #1735 had to add -skip to terminate. Likely a goroutine/channel deadlock or a waitgroup that never closes.

[Kpa-clawbot]

Severity: P2 — blocks go test ./... reliability and CI signal in cmd/server.

Claim: confirmed. cmd/server/bounded_load_test.go:86 TestBoundedLoad_OldestLoadedSet exists; PR #1735's local runs deliberately -skip TestBoundedLoad to terminate. Sibling tests in the same file (TestBoundedLoad_LimitedMemory, _NewestFirst, _UnlimitedWithZero, _AscendingOrder) presumably run, so the hang is specific to this case.

Code today: cmd/server/bounded_load_test.go:86-100. Uses createTestDB(t, 5000) + loadStore(t, dbPath, 1) (1MB cap). Asserts store.oldestLoaded is set and matches store.packets[0].FirstSeen.

Findings:

• (house): "Hangs reliably" + sibling tests with the same fixture passing → not a deadlock in shared infra. Likely a goroutine launched by loadStore with maxMemoryMB=1 (vs 0/unbounded in siblings) — bounded path triggers a background loader / channel that nobody closes when test scope is just 5000 rows.
• (kent-beck): Repro first, then bisect: run with -run TestBoundedLoad_OldestLoadedSet -timeout 30s and capture SIGQUIT goroutine dump. Don't speculate before reading the stack.

Fix path: reproduce locally with timeout + goroutine dump → find the leaked goroutine → either close it on t.Cleanup or fix the production path. Effort: M (diagnosis-dependent). Worst case quarantine with t.Skip("see #1741") to unblock CI; do NOT ship the skip without a goroutine dump attached to this issue.

Dup check: searched "TestBoundedLoad hang" — none.

Triage verdict: ready-to-fix