Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44112

The ChangeStream test fails on the latest sharded cluster

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Query 2019-11-04, Query 2019-11-18, Query 2019-12-02

      There is one change stream JSON test that fails on the latest sharded cluster. Reproducible at least on c# and Java drivers.

      Json test: https://github.com/mongodb/specifications/blob/master/source/change-streams/tests/change-streams-errors.json#L76

      It looks like the reason of it that the latest server doesn't throw `280` error for the test "Change Stream should error when _id is projected out" anymore:
      https://github.com/mongodb/specifications/blob/master/source/change-streams/tests/change-streams-errors.json#L103
      So, our test runner doesn't catch the expected error and then fails.

      The evergreen task: https://evergreen.mongodb.com/task_log_raw/dot_net_driver_unsecure_tests__version~latest_os~windows_64_topology~sharded_cluster_auth~noauth_ssl~nossl_test_f809794cf52538bd3f6b5c5ba5b9a74b17257fb7_19_10_17_23_46_15/2?type=T#L2824

            Assignee:
            justin.seyster@mongodb.com Justin Seyster
            Reporter:
            dmitry.lukyanov@mongodb.com Dmitry Lukyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: