Repository navigation
Commit c5be421
test(plugin): raise Bun test timeout to 30s so SQLite locks surface first
Extracted from PR #338 (Cole Leavitt). Bun's default 5s test timeout and
SQLite's production 5s busy_timeout currently hide a real lock wait behind
the same wall-clock cutoff, so a shared-DB contention surfaces as an
unattributable Bun timeout instead of a visible SQLITE_BUSY error. Raising
the test timeout to 30s lets the lock error report first.
This is observability work for #312, NOT a fix: it does not isolate per-file
databases or change the test busy_timeout, so the shared context.db
contention remains open.
Co-Authored-By: Cole Leavitt <[email protected]>
Co-Authored-By: Alfonso <[email protected]>1 parent 9510e68 commit c5be421
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
42 | | - | |
| 42 | + | |
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
| |||
0 commit comments