-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Environment:Windows debug build
-
Windows
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The debug Windows build takes (for example) 6705 seconds to fail in jstests/sharding/auth.js, while the Windows release build succeeds in 749 seconds (i.e. almost 9 times as long).
http://buildlogs.mongodb.org/build/5007c268d2a60f222e000450/test/50081448d2a60f22f4000539/
assert: command failed: { Error("Printing Stack Trace")@:0 ()@src/mongo/shell/utils.js:37 ("command failed: {\n\t\"ok\" : 0,\n\t\"errmsg\" : \"MR post processing failed: { result: \\\"mrout\\\", errmsg: \\\"exception: getMore: cursor didn't exist on server, possible restart or timeout?\\\", code: 13127, ok: 0.0 }\"\n} : undefined")@src/mongo/shell/utils.js:58 ([object bson_object])@src/mongo/shell/utils.js:217 @D:\slave\Windows_64bit_2008+_DEBUG\mongo\jstests\sharding\auth.js:241 Thu Jul 19 15:27:35 uncaught exception: command failed: { "ok" : 0, "errmsg" : "MR post processing failed: { result: \"mrout\", errmsg: \"exception: getMore: cursor didn't exist on server, possible restart or timeout?\", code: 13127, ok: 0.0 }" } : undefined failed to load: D:\slave\Windows_64bit_2008+_DEBUG\mongo\jstests\sharding\auth.js } : undefined
Testing locally, I couldn't reproduce either the failure or the huge time difference from the release build. The debug build worked in VirtualBox under Linux and finished in 32 minutes versus 13 minutes for the release build (about 2.5 times as long).