Ugh ugh ugh.

The Buildbot Windows 32-bit builders (master and nightly) are HANGING on sharding/complex_sharding.js

Here is one example:

Nightly Windows 32-bit Build #1402 Friday Aug 23 (rev b283169ae51)

http://buildbot.10gen.cc/builders/Nightly%20Windows%2032-bit/builds/1402/steps/mongosTest_smokeSharding/logs/stdio

 *******************************************
         Test : complex_sharding.js ...
      Command : ...
         Date : Fri Aug 23 18:04:09 2013
                (output suppressed; see http://buildlogs.mongodb.org/build/5217706ad2a60f2040000824/test/5217a41ad2a60f3124000158/)
...
command timed out: 10800 seconds without output, attempting to kill
                  345.9525 minutes

The log saved to buildlogger is huge. For that specific build, `http://buildlogs.mongodb.org/Nightly%20Windows%2032-bit/builds/1402/test/sharding/complex_sharding.js?mode=raw` is 286MB.

Most of this file consists of this line repeated...

 m31200| 2013-08-23T18:04:16.736+0000 [rsSyncNotifier] replset markOplog: 0:0 5217a420:1

That line appears 3,372,664 times, right unto the very end.

This is not impacting MCI because it has no 32-bit Windows builders.

This morning, I noticed that the nightly Win32 builder had not run by 9am because the master builder was still running. In retrospect, it was hanging on complex_sharding.js. Then the nightly builder hung in precisely the same way.