buildscripts/smoke.py --nojournal --small-oplog jstests/connections_opened.js

https://bamboo.10gen.com/browse/MONGODB-COMMITLINUX-SMALLOPLOG-211/log

From what I can tell, it seems like the problem is that when the test starts it starts a resync, at some point that resync finishes and closes the connection it was using, causing the connection numbers to be off by one in the test.

The solution may be just to skip this test when running with small oplog (there's already a section of smoke.py for skipping tests when running with small oplog), but I don't know enough about how master/slave works and why this resync is happening to tell if there's a better way (perhaps by preventing the resync, waiting for it to terminate before starting the test, or somehow preventing it from messing with the connection numbers).