Skip to content

Add fsyncUnlock command tests#641

Open
danielfrankcom wants to merge 4 commits into
documentdb:mainfrom
danielfrankcom:pr/fsyncUnlock
Open

Add fsyncUnlock command tests#641
danielfrankcom wants to merge 4 commits into
documentdb:mainfrom
danielfrankcom:pr/fsyncUnlock

Conversation

@danielfrankcom

@danielfrankcom danielfrankcom commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

This change adds tests for the fsyncUnlock administration command.

This command affects global state, so it uses the no_parallel mark, and also has an autouse fixture which makes sure we have a clean state before running each test.

Closes #421

Signed-off-by: Daniel Frankcom <frankcom@amazon.com>
@danielfrankcom danielfrankcom requested a review from a team as a code owner June 23, 2026 21:45
@documentdb-triage-tool documentdb-triage-tool Bot added compatibility test Compatibility test related enhancement New feature or request labels Jun 23, 2026
@documentdb-triage-tool

Copy link
Copy Markdown

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, enhancement
Project fields suggested: Component test-framework · Priority P2 · Effort M · Status Needs Review
Confidence: 0.88 (mixed)

Reasoning

component from path globs (test-framework, test-coverage); effort from diff stats (403+2 LOC, 3 files); LLM: Adds new test coverage for the fsyncUnlock command in the compatibility test suite, a straightforward test addition.

If a label is wrong, remove it manually and ping @patty-chow so the rules can be tuned. The bot will not re-label items that already have component labels.

Signed-off-by: Daniel Frankcom <frankcom@amazon.com>
Signed-off-by: Daniel Frankcom <frankcom@amazon.com>
Upstream's declarative-environments rework (documentdb#617) replaced the single
config.connection_string attribute with per-target parametrization,
exposing the current target's string via the connection_string fixture.
The merge left test_fsyncUnlock_releases_lock_taken_on_another_connection
reading pytestconfig.connection_string, which no longer exists and fails
at runtime with AttributeError on every target.

Take the second client's connection string from the connection_string
fixture instead.

Signed-off-by: Daniel Frankcom <frankcom@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

compatibility test Compatibility test related enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add compatibility test for fsyncUnlock

2 participants