GitHub deploy run 32587841233 failed after the gateway compile fix because TestClaimTurnConcurrentInsertRaceNeverReturnsAnError launched 200 concurrent SQLite claims and exhausted its immediate retry loop with SQLITE_BUSY. The test's stated target is the two-connection same-turn insert race, not unrelated global write-lock saturation.
Acceptance criteria
The regression still races two independent stores over the same turn ID; unrelated cross-trial SQLite contention cannot exhaust retries; repeated focused runs, task check, and diff-scoped lint pass; fresh adversarial review has zero surviving findings.
Close reason
Already fixed on main: session_store_sqlite_claimturn_race_test.go now runs the 100 trials serially (two stores racing one turn ID per trial) with bounded SQLITE_BUSY retries, instead of 200 concurrent claims. Verified: -count=3 passes.
Imported from beads archie-core-mzok · GitHub #587 · type bug · priority P0 · created 2026-08-22 · closed 2026-08-24
GitHub deploy run 32587841233 failed after the gateway compile fix because TestClaimTurnConcurrentInsertRaceNeverReturnsAnError launched 200 concurrent SQLite claims and exhausted its immediate retry loop with SQLITE_BUSY. The test's stated target is the two-connection same-turn insert race, not unrelated global write-lock saturation.
### Acceptance criteria
The regression still races two independent stores over the same turn ID; unrelated cross-trial SQLite contention cannot exhaust retries; repeated focused runs, task check, and diff-scoped lint pass; fresh adversarial review has zero surviving findings.
### Close reason
Already fixed on main: session_store_sqlite_claimturn_race_test.go now runs the 100 trials serially (two stores racing one turn ID per trial) with bounded SQLITE_BUSY retries, instead of 200 concurrent claims. Verified: -count=3 passes.
---
_Imported from beads `archie-core-mzok` · GitHub #587 · type bug · priority P0 · created 2026-08-22 · closed 2026-08-24_
sam
added the criticalbug labels 2026-10-27 13:40:29 +00:00
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.
GitHub deploy run 32587841233 failed after the gateway compile fix because TestClaimTurnConcurrentInsertRaceNeverReturnsAnError launched 200 concurrent SQLite claims and exhausted its immediate retry loop with SQLITE_BUSY. The test's stated target is the two-connection same-turn insert race, not unrelated global write-lock saturation.
Acceptance criteria
The regression still races two independent stores over the same turn ID; unrelated cross-trial SQLite contention cannot exhaust retries; repeated focused runs, task check, and diff-scoped lint pass; fresh adversarial review has zero surviving findings.
Close reason
Already fixed on main: session_store_sqlite_claimturn_race_test.go now runs the 100 trials serially (two stores racing one turn ID per trial) with bounded SQLITE_BUSY retries, instead of 200 concurrent claims. Verified: -count=3 passes.
Imported from beads
archie-core-mzok· GitHub #587 · type bug · priority P0 · created 2026-08-22 · closed 2026-08-24