summaryrefslogtreecommitdiff
path: root/jstests/libs
diff options
context:
space:
mode:
authorMax Hirschhorn <max.hirschhorn@mongodb.com>2014-10-06 21:04:23 -0400
committerDan Pasette <dan@mongodb.com>2014-10-06 22:07:39 -0400
commit47e6a29b3b1dc119afb15d1597d506031ba760ab (patch)
tree2103acc4ca1b92db8cc233e54a642e37cb72e7b7 /jstests/libs
parent39bdeb3268493f9a56ad688d64d9d0273ba31ad7 (diff)
downloadmongo-47e6a29b3b1dc119afb15d1597d506031ba760ab.tar.gz
SERVER-15532 Fix assumptions made by geo_s2cursorlimitskip.js test.
For storage engines that are transactional, the documents that are inserted after the creation of a cursor need not be visible to the cursor. This means that the set of points inserted after the query is issued may not be found, depending on the storage engine. Note that this test can no longer be run in parallel because we assert a specific number of query and getmore operations have occurred. Signed-off-by: Dan Pasette <dan@mongodb.com>
Diffstat (limited to 'jstests/libs')
-rw-r--r--jstests/libs/parallelTester.js1
1 files changed, 1 insertions, 0 deletions
diff --git a/jstests/libs/parallelTester.js b/jstests/libs/parallelTester.js
index 8c44d2df553..642a534de18 100644
--- a/jstests/libs/parallelTester.js
+++ b/jstests/libs/parallelTester.js
@@ -161,6 +161,7 @@ if ( typeof _threadInject != "undefined" ){
// These tests expect the profiler to be on or off at specific points
// during the test run.
parallelFilesDir + "/cursor6.js",
+ parallelFilesDir + "/geo_s2cursorlimitskip.js",
parallelFilesDir + "/profile2.js",
parallelFilesDir + "/updatee.js"
];