mirror
/
mongo
mirror of https://github.com/mongodb/mongo
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SERVER-106487 point_in_time_lookups_drop_pending.js is flaky when checking that a PIT read creates a new instance for the collection after a drop (#38242) 

GitOrigin-RevId: dcbeacd2587f3c3000119beceb195b15306dd5de
This commit is contained in:
Pol Piñol Castuera 2025-07-09 11:43:43 +02:00 committed by MongoDB Bot
parent 4a1370a9a7
commit 353feeecfd
1 changed files with 1 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
jstests/noPassthrough/catalog/point_in_time_lookups_drop_pending.js
View File

@ -41,9 +41,6 @@ jsTestLog("Create index timestamp: " + tojson(createIndexTS));
const dropTS = assert.commandWorked(db.runCommand({drop: jsTestName()})).operationTime;
jsTestLog("Drop collection timestamp: " + tojson(dropTS));
// Instantiate a new collection without any shared state.
assert(checkLog.checkContainsWithCountJson(db, 6825401, {}, 0));
// Test that we can perform a point-in-time read from a drop pending table using an index.
let res = assert.commandWorked(db.runCommand({
find: jsTestName(),
@ -52,7 +49,4 @@ let res = assert.commandWorked(db.runCommand({
}));
assert.eq(kNumDocs, res.cursor.firstBatch.length);
// Instantiate a new collection without any shared state.
checkLog.containsJson(db, 6825401);
rst.stopSet();
rst.stopSet();