-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
ALL
This caused the following buildbot failure:
<http://buildbot.mongodb.org/builders/V2.0%20Linux%20RHEL%2064-bit/builds/223/steps/test_1/logs/stdio>
assert failed : C : { "ts" : ISODate("2012-08-28T07:57:44.401Z"), "op" : "insert", "ns" : "test.jstests_distinct3", "millis" : 0, "client" : "127.0.0.1", "user" : "" } Error("Printing Stack Trace")@:0 ()@shell/utils.js:35 ("assert failed : C : {\n\t\"ts\" : ISODate(\"2012-08-28T07:57:44.401Z\"),\n\t\"op\" : \"insert\",\n\t\"ns\" : \"test.jstests_distinct3\",\n\t\"millis\" : 0,\n\t\"client\" : \"127.0.0.1\",\n\t\"user\" : \"\"\n}")@shell/utils.js:46 (false,"C : {\n\t\"ts\" : ISODate(\"2012-08-28T07:57:44.401Z\"),\n\t\"op\" : \"insert\",\n\t\"ns\" : \"test.jstests_distinct3\",\n\t\"millis\" : 0,\n\t\"client\" : \"127.0.0.1\",\n\t\"user\" : \"\"\n}")@shell/utils.js:54 @/data/buildslaves/Linux_RHEL_64bit_V2.0/mongo/jstests/evalb.js:14 Tue Aug 28 03:57:44 uncaught exception: assert failed : C : { "ts" : ISODate("2012-08-28T07:57:44.401Z"), "op" : "insert", "ns" : "test.jstests_distinct3", "millis" : 0, "client" : "127.0.0.1", "user" : "" }
- distinct3.js starts a parallel shell that does several writes without a read or get last error. distinct3.js waits for the parallel shell to finish but not for the writes triggered by the parallel shell to complete. As a result, the writes may continue into the next test. (Generally this will not cause problems because the writes are to the jstests_distinct3 collection, but we should probably clean it up.)
- The evalb test turns on profiling for the test database and then assumes it is the only script generating operations for profiling. This is not a valid assumption in the parallel or small oplog test suites. The fix would probably be similar to the
SERVER-5293fix.