Test failure - test_streaming_protocol.TestStreamingProtocol.test_monitor_waits_after_server_check_error

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.11
    • Affects Version/s: None
    • Component/s: Tests
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test started failed after PYTHON-2299

      [2020/07/08 22:19:27.088] FAIL [2.035s]: test_monitor_waits_after_server_check_error (test_streaming_protocol.TestStreamingProtocol)
[2020/07/08 22:19:27.088] ----------------------------------------------------------------------
[2020/07/08 22:19:27.088] Traceback (most recent call last):
[2020/07/08 22:19:27.088]   File "/data/mci/2eefa036962608665fecae269fa90a42/src/test/__init__.py", line 444, in wrap
[2020/07/08 22:19:27.088]     return f(*args, **kwargs)
[2020/07/08 22:19:27.088]   File "/data/mci/2eefa036962608665fecae269fa90a42/src/test/test_streaming_protocol.py", line 193, in test_monitor_waits_after_server_check_error
[2020/07/08 22:19:27.088]     self.assertTrue(hb_succeeded_events[1].awaited)
[2020/07/08 22:19:27.088] AssertionError: False is not true

      https://evergreen.mongodb.com/task/mongo_python_driver_tests_python_version_rhel62_test_ssl__platform~rhel62_auth~noauth_ssl~nossl_python_version~3.5_coverage~coverage_test_latest_replica_set_065001ef2e419cf53b95b91e9fdb5e4e8e75fc5a_20_07_08_21_51_17

      I suspect the cause is a race in the tests which leads to fewer heartbeat events than expected.

              Assignee:
              Shane Harvey
              Reporter:
              Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: