rust/lancedb
1
0
Fork 0
mirror of https://github.com/lancedb/lancedb.git synced 2026-11-13 22:26:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

test: isolate DynamoDB integration test databases (#4998)

Browse Source 
The concurrent-append and drop-all DynamoDB tests shared a database
prefix. A timeout in the first could leave its table visible to the
second. Give each test its own prefix while retaining five independent
concurrent appends, the six-row assertion, and all drop/recreate checks.

The final two-prefix diff passed both tests in hosted LocalStack across
Node 22, 24, 26, and Node 24 experimental, without timing
instrumentation ([run
43245851764](https://github.com/lancedb/lancedb/actions/runs/43245851764),
head `5896c419`). Concurrency and the 5000 ms budget are unchanged. This
fixes cascading fixture contamination; the original timeout remains
unexplained, and these passing runs do not prove its root cause was
fixed.
This commit is contained in:
Xuanwo
2026-11-13 00:22:35 +08:00
committed by GitHub
parent b5623f8881
commit b4d1c55f62
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
nodejs/__test__/s3_integration.test.ts
+2 -2
View File
@@ -282,7 +282,7 @@ maybeDescribe("DynamoDB Lock", () => {
});
it("can be used to configure a DynamoDB table for commit log", async () => {
const uri = `s3+ddb://${bucket.name}/test?ddbTableName=${commitTable.name}`;
const uri = `s3+ddb://${bucket.name}/concurrent-appends?ddbTableName=${commitTable.name}`;
const db = await connect(uri, {
storageOptions: CONFIG,
readConsistencyInterval: 0,
@@ -307,7 +307,7 @@ maybeDescribe("DynamoDB Lock", () => {
});
it("clears dynamodb state after dropping all tables", async () => {
const uri = `s3+ddb://${bucket.name}/test?ddbTableName=${commitTable.name}`;
const uri = `s3+ddb://${bucket.name}/drop-all-tables?ddbTableName=${commitTable.name}`;
const db = await connect(uri, {
storageOptions: CONFIG,
readConsistencyInterval: 0,