This isn't a driver bug, but a general problem in our tests that use the monitoring framework when running with authentication. These kinds of tests need to ignore events that are not the event they are looking for. The behavior in this failure should be expected and worked around.
====================================================================== FAIL: test_max_await_time_ms (test_cursor.TestCursor) ---------------------------------------------------------------------- Traceback (most recent call last): File "/mnt/jenkins/workspace/mongo-python-driver-auth/extensions/without-extensions/label/linux64/mongodb_configuration/replica_set/mongodb_option/noauth/mongodb_server/32-release/python_language_version/2.6/test/__init__.py", line 324, in wrap return f(*args, **kwargs) File "/mnt/jenkins/workspace/mongo-python-driver-auth/extensions/without-extensions/label/linux64/mongodb_configuration/replica_set/mongodb_option/noauth/mongodb_server/32-release/python_language_version/2.6/test/test_cursor.py", line 261, in test_max_await_time_ms self.assertEqual('find', results['started'][0].command_name) AssertionError: 'find' != 'saslContinue' - find + saslContinue