[SERVER-33] n:2 test fails in pair4.js test Created: 30/Apr/09  Updated: 12/Jul/16  Resolved: 19/May/09

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

<http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/176/steps/test_3/logs/stdio>

{"_id" : "49f9c4df9c9cb939d893ecd0" , "n" : 2 , "m" : 3}

(mongo init):888 assert.soon failed: function () {
obj = coll( c ).findOne(

{n:2}

);
printjson( obj );
return obj.m == undefined;
}, msg:n:2 test for mongo connection to 127.0.0.1:38616 failed
throw "assert.soon failed: " + f + ", msg:" + msg;
^



 Comments   
Comment by Aaron Staple [ 19/May/09 ]

test exposed a race condition, which I fixed

Comment by Aaron Staple [ 19/May/09 ]

Now with even more debugging

<http://buildbot.mongodb.org/builders/OS%20X%2010.5%2064-bit/builds/318/steps/test_3/logs/stdio>

Comment by Aaron Staple [ 13/May/09 ]

Sweet, this failed run has the verbose output:

<http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/280/steps/test_3/logs/stdio>

Comment by Aaron Staple [ 13/May/09 ]

There's no indication that the slave is seeing the new op that should be created by the master as it processes the $set.

Now running the mongod instances in very verbose mode, maybe we'll see something interesting.

Comment by Aaron Staple [ 06/May/09 ]

again

<http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/203/steps/test_3/logs/stdio>

Generated at Thu Feb 08 02:52:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.