test: raise ANN plan-check timeout for slow CI runners - #274
Merged
Conversation
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.
This was referenced Aug 25, 2026
Merged
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The result-level ANN plan-check test (
tests/turso-vector-search.test.ts) seeds 200 vectors and performs a realvector_top_ksearch. On slower CI runners — consistently onwindows-latestin the current release gate — this exceeds bun's default 5s per-test timeout even though the assertions pass locally and on every other OS.Give that single integration-style test explicit 30s headroom; no assertion changes.
Evidence