Test Failure - test_max_staleness.TestMaxStaleness.test_last_write_date

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • 3.8
    • Affects Version/s: 3.7
    • Component/s: Tests
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      test_max_staleness.TestMaxStaleness.test_last_write_date failed in Evergreen:

       FAILURE: 1530040938.0 not greater than 1530040938.0 (AssertionError)
 Traceback (most recent call last):
   File "/data/mci/0f2a18c7f52d53a62bb4706481db156d/src/test/__init__.py", line 404, in wrap
     return f(*args, **kwargs)
   File "/data/mci/0f2a18c7f52d53a62bb4706481db156d/src/test/__init__.py", line 404, in wrap
     return f(*args, **kwargs)
   File "/data/mci/0f2a18c7f52d53a62bb4706481db156d/src/test/test_max_staleness.py", line 132, in test_last_write_date
     self.assertGreater(server.description.last_write_date, last_write)
 AssertionError: 1530040938.0 not greater than 1530040938.0
 system-out:

      https://evergreen.mongodb.com/task/mongo_python_driver_tests_python_version_green_framework_rhel62__auth_ssl~noauth_nossl_python_version~2.7_green_framework~gevent_test_latest_replica_set_35391b7c2cbd78e748850e6879323a6c746e4bdf_18_06_26_18_08_42

      I believe this is just a race condition in the test suite. We should either increase the sleep time after the second write or we should decrease the heartbeatFrequencyMS for this test.

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

              Created:
              Updated:
              Resolved: