Temporarily block failing tests in Per Shard Cursor passthrough suite

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • QE 2022-02-21, QE 2022-03-07
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As we work on resolving all of the bugs in the change_streams_per_shard_cursor_passthrough suite, we want to temporarily block the failing tests so that we can work through the test failures one at a time, and merge what we have to allow the replicator to begin work around it.

      The failing tests are:

      • jstests/change_streams/apply_ops_resumability.js
      • jstests/change_streams/apply_ops.js
      • jstests/change_streams/does_not_implicitly_create_database.js
      • jstests/change_streams/metadata_notifications.js
      • jstests/change_streams/oplog_rewrite/change_stream_null_existence_eq_rewrite_test.js
      • jstests/change_streams/report_post_batch_resume_token.js
      • jstests/change_streams/resume_from_high_water_mark_token.js
      • jstests/change_streams/shell_helper.js
      • jstests/change_streams/start_after_invalidation_exception.js
      • jstests/change_streams/whole_db_resumability.js
      • jstests/change_streams/whole_db.js

            Assignee:
            Mickey Winters
            Reporter:
            Jennifer Peshansky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: