Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-4670

Fix failing consecutive resume change stream test

    • Type: Icon: Build Failure Build Failure
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 2
    • Not Needed
    • Not Needed

      When the async interval was fixed in NODE-4638, the change stream consecutive resume spec test started failing.  There appears to be a race condition - after initializing the change stream and inserting multiple documents, when the CS is iterated, no events are received.  Adding a write concern of 'w': 'majority' to the inserts or adding a short sleep after the inserts is enough to allow the test to consistently pass.

      Acceptance Criteria

      • Determine the root cause of the failing test and fix the test
      • Unskip the two skipped consecutive resume change stream tests
      • Remove the manually added prose test

            Assignee:
            bailey.pearson@mongodb.com Bailey Pearson
            Reporter:
            bailey.pearson@mongodb.com Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: