From fcd3d1cd1498efc2e15447ed12eaded49e71f430 Mon Sep 17 00:00:00 2001 From: Karl Seguin Date: Mon, 20 Apr 2026 18:14:29 +0800 Subject: [PATCH] Use unsafe journal_mode during Pool test Can't use WAL, as it thread sanitizer reports false positives. The default, delete, causes busy timeouts. Let's try the unsafe memory! --- src/storage/sqlite/Pool.zig | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/storage/sqlite/Pool.zig b/src/storage/sqlite/Pool.zig index 38a88d46..a06d5e10 100644 --- a/src/storage/sqlite/Pool.zig +++ b/src/storage/sqlite/Pool.zig @@ -117,6 +117,11 @@ test "Sqlite: Pool" { // because the tests might be run on really slow hardware and we // want to avoid having a busy timeout. try conn.exec("pragma synchronous=off", .{}); + + // Also not safe, but we're trying to avoid busy timeouts without using + // WAL mode, which can trigger false positives in thread-sanitizer + try conn.exec("pragma journal_mode=memory", .{}); + try conn.exec("create table pool_test (cnt int not null)", .{}); try conn.exec("insert into pool_test (cnt) values (0)", .{}); }