summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEliot Horowitz <eliot@10gen.com>2012-05-28 23:38:49 -0400
committerEliot Horowitz <eliot@10gen.com>2012-05-28 23:39:16 -0400
commit3f33add676650e5dcdd5f805249f251bb87dbcf2 (patch)
tree7f81c7269871a12c347f76748ed261dbd4d4ba5c
parent7c6ad5669d859fe6e2fbbdd5233c69fb7536db73 (diff)
downloadmongo-3f33add676650e5dcdd5f805249f251bb87dbcf2.tar.gz
remove race condition test and add another check because the asserts in log are normal but scary
-rw-r--r--jstests/repl/repl13.js8
1 files changed, 8 insertions, 0 deletions
diff --git a/jstests/repl/repl13.js b/jstests/repl/repl13.js
index 119b03c7d80..e8a80966dab 100644
--- a/jstests/repl/repl13.js
+++ b/jstests/repl/repl13.js
@@ -35,8 +35,10 @@ for( i = 99999; i >= 90000; --i ) {
// The initial sync completes and subsequent writes succeed, in spite of any assertions that occur
// when the update operations above are replicated.
mc.save( {} );
+assert.eq( 100001 , mc.count() );
assert.soon( function() { return sc.count() == 100001; } );
mc.save( {} );
+assert.eq( 100002 , mc.count() );
assert.soon( function() { return sc.count() == 100002; } );
debug( sc.findOne( {_id:99999} ) );
@@ -44,3 +46,9 @@ debug( sc.findOne( {_id:90000} ) );
assert.eq( 1, sc.findOne( {_id:99999} ).a );
assert.eq( 1, sc.findOne( {_id:90000} ).a );
+
+m_hash = m.getDB( "d" ).runCommand( "dbhash" );
+s_hash = s.getDB( "d" ).runCommand( "dbhash" );
+
+assert.eq( m_hash.collections.c , s_hash.collections.c , "sad " + tojson( m_hash ) + " " + tojson( s_hash ) );
+