From bc8e6d61bb6ac5849274b9dfa711b34d66b53b82 Mon Sep 17 00:00:00 2001 From: Zhafron Date: Tue, 25 Aug 2026 12:06:07 +0700 Subject: [PATCH] test: raise ANN plan-check timeout for slow CI runners The result-level ANN validation seeds 200 vectors and runs a real vector_top_k search; on windows-latest runners this can exceed the default 5s test timeout even though the behavior under test is correct. Give it explicit headroom instead of leaving the release gate flaky. --- tests/turso-vector-search.test.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tests/turso-vector-search.test.ts b/tests/turso-vector-search.test.ts index 51e2b7c..e498b7b 100644 --- a/tests/turso-vector-search.test.ts +++ b/tests/turso-vector-search.test.ts @@ -101,6 +101,9 @@ describe("turso vector search", () => { expect(observedSql[1]).toContain("m.container_tag = ?"); }); + // Seeding 200 vectors plus a real ANN search can exceed bun's default 5s test + // timeout on slower CI runners (observed on windows-latest), so give this + // integration-style check explicit headroom. The assertions are unchanged. it("returns correct tagged memories from ANN above the k threshold (result-level plan check)", async () => { baseDir = mkdtempSync(join(tmpdir(), "turso-vector-ann-")); @@ -166,5 +169,5 @@ describe("turso vector search", () => { } // Results should be limited to the requested limit. expect(results.length).toBeLessThanOrEqual(10); - }); + }, 30000); });