Skip to content

Fix SQLite pool-sensitive test cleanup - #2620

Merged
Widthdom merged 2 commits into
mainfrom
fix-issue1668
May 24, 2026
Merged

Fix SQLite pool-sensitive test cleanup#2620
Widthdom merged 2 commits into
mainfrom
fix-issue1668

Conversation

@Widthdom

Copy link
Copy Markdown
Owner

Summary

  • Add a serialized xUnit collection fixture for SQLite pool-sensitive tests.
  • Centralize collection-boundary SQLite pool clearing in SqlitePoolCleanup.
  • Add regression tests for fixture registration and cleanup behavior.

Validation

  • dotnet build
  • dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --framework net8.0 --filter "FullyQualifiedName~SqlitePoolSensitiveCollectionTests|FullyQualifiedName~ConcurrencyTests"
  • dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --framework net9.0 --filter "FullyQualifiedName~SqlitePoolSensitiveCollectionTests|FullyQualifiedName~ConcurrencyTests"
  • dotnet run --project tools/CodeIndex.Changelog -- check
  • Adversarial review: No blocking/actionable issues found.

Documentation and changelog

  • Added changelog.d/unreleased/1668.fixed.md.
  • No AGENTS.md, CLAUDE.md, or AGENT_GUIDE.md changes.

Follow-up candidates

  • None.

Fixes #1668

@Widthdom
Widthdom marked this pull request as ready for review May 24, 2026 10:52
@Widthdom
Widthdom merged commit 4a0dc48 into main May 24, 2026
10 checks passed
@Widthdom
Widthdom deleted the fix-issue1668 branch May 24, 2026 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SQLite connection pool not test-case-isolated within xUnit collection; pool dirty after test failure

1 participant