do a db.error at the end of each teardown. hopefully this will fix the out of order messages that we've been experiencing

tests/test_admin.rb

@@ -22,6 +22,7 @@ class AdminTest < Test::Unit::TestCase
   def teardown
     @admin.profiling_level = :off
     @@coll.clear if @@coll
+    @@db.error
   end
 
   def test_default_profiling_level

tests/test_chunk.rb

@@ -24,6 +24,7 @@ class ChunkTest < Test::Unit::TestCase
   def teardown
     @@chunks.clear
     @@files.clear
+    @@db.error
   end
 
   def test_pos

tests/test_cursor.rb

@@ -19,6 +19,7 @@ class CursorTest < Test::Unit::TestCase
 
   def teardown
     @@coll.clear
+    @@db.error
   end
 
   def test_explain

tests/test_db.rb

@@ -29,6 +29,7 @@ class DBTest < Test::Unit::TestCase
 
   def teardown
     @@users.clear if @@users
+    @@db.error
   end
 
   def test_close

tests/test_db_api.rb

@@ -19,6 +19,7 @@ class DBAPITest < Test::Unit::TestCase
 
   def teardown
     @@coll.clear
+    @@db.error
   end
 
   def test_clear

tests/test_db_connection.rb

@@ -13,5 +13,6 @@ class DBConnectionTest < Test::Unit::TestCase
     db = Mongo.new(host, port).db('ruby-mongo-demo')
     coll = db.collection('test')
     coll.clear
+    db.error
   end
 end

tests/test_grid_store.rb

@@ -22,6 +22,7 @@ class GridStoreTest < Test::Unit::TestCase
   def teardown
     @@chunks.clear
     @@files.clear
+    @@db.error
   end
 
   def test_exist

tests/test_mongo.rb

@@ -13,6 +13,10 @@ class MongoTest < Test::Unit::TestCase
     @mongo = Mongo.new(@host, @port)
   end
 
+  def teardown
+    @mongo.db('ruby-mongo-test').error
+  end
+
   def test_database_info
     @mongo.drop_database('ruby-mongo-info-test')
     @mongo.db('ruby-mongo-info-test').collection('info-test').insert('a' => 1)