Test failure - test_change_stream.TestCollectionChangeStream.test_concurrent_close

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Tests
    • None
    • 🔵 Done
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      This test fails fairly often:

       [2020/05/07 03:15:31.548] FAIL [4.118s]: test_concurrent_close (test_change_stream.TestCollectionChangeStream)
 [2020/05/07 03:15:31.549] Ensure a ChangeStream can be closed from another thread.
 [2020/05/07 03:15:31.550] ----------------------------------------------------------------------
 [2020/05/07 03:15:31.550] Traceback (most recent call last):
 [2020/05/07 03:15:31.550]   File "/data/mci/56b896f56a4f6504ef8cab5cbc5da303/src/test/test_change_stream.py", line 340, in test_concurrent_close
 [2020/05/07 03:15:31.550]     self.assertFalse(t.is_alive())
 [2020/05/07 03:15:31.550] AssertionError: True is not false

      For example, this patch build: https://evergreen.mongodb.com/task/mongo_python_driver_tests_python_version_rhel62_test_ssl__platform~rhel62_auth~noauth_ssl~nossl_python_version~2.7_coverage~coverage_test_latest_sharded_cluster_patch_ae5c03df17023e5596b1a64129b9ad9fa7be4ad1_5eb37a960305b91e599086af_20_05_07_03_04_22

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

                Created:
                Updated:
                Resolved: