Repository navigation
Tests in SqliteCommandTest are flaky #35585
Description
Flaky tests:
ExecuteReader_retries_when_lockedExecuteReader_retries_when_busyExecuteScalar_throws_when_busy_with_returningExecuteNonQuery_throws_when_busy_with_returningExecuteReader_throws_when_busy_with_returningExecuteReader_throws_when_busy_with_returning_while_draining
Error:
Microsoft.Data.Sqlite.SqliteException : SQLite Error 1: 'no such table: Data'.
These failures don't seem to be platform-specific.
Activity
Make the busy tests prove they waited, and keep the skipped ones honest
Manish-1kumar commentedon Nov 3, 2026
I've submitted a fix for this in PR #39510.
Root cause: All six skipped tests used hardcoded shared SQLite database names (locked, �usy.db,
eturning.db). When tests run in parallel, they collide on the same database, causing spurious
o such table: Data errors and lock-contention failures.
Fix: Replace hardcoded names with Guid.NewGuid():N-prefixed unique names per test invocation. This eliminates all cross-test state bleed without changing any test assertions or retry logic.
Results: All 6 previously-skipped tests now pass. Full suite: 814 passed, 1 skipped (the unrelated Collations_dont_bleed_across_connections skip for ericsink/SQLitePCL.raw#421), 0 failed.
Fix flaky SqliteCommandTest concurrency tests by using unique databas…