Repository navigation
test: give the DropIndex concurrency tests a load-tolerant lock timeout - #324
Merged
Merged
Conversation
DynamicCollection_DropIndex_WaitsForTheCollectionLock and DynamicCollection_DropIndex_WhileInserting failed intermittently on CI with lock timeouts: eight writers and a drop contend for the collection lock, and the 500 ms default is too short on a loaded runner. The tests check ordering and consistency, not lock latency, so they open the engine with 30 s locks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mrdevrobot
had a problem deploying
to
Production
October 18, 2026 20:36 — with 
GitHub Actions
Failure
GitHub Actions
Failure
This branch was successfully deployed
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.
Two tests added in #239 fail intermittently on CI with lock timeouts (three times in the last runs on main and on PRs):
DynamicCollection_DropIndex_WaitsForTheCollectionLockandDynamicCollection_DropIndex_WhileInserting_KeepsCollectionAndOtherIndexConsistent. Eight writers and a drop contend for the collection lock, and the 500 ms default is too short on a loaded runner. The tests check ordering and consistency, not lock latency, so they now open the engine with 30 s locks; the assertions are unchanged (the drop is still checked to wait while the lock is held).Test-only change. The other known flaky tests (CrossCollectionWriteRaceTests, CdcScalabilityTests, MetricsTests) are not touched here.
🤖 Generated with Claude Code