Restore minServerVersion in server-discovery-and-monitoring integration tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing
    • 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

      We have an issue with comparing serverVersions in release candidate.

      For example, the current 4.4 server version on EG is {4.4.0-rc13-11-g97cd266} and considered less than 4.4. And since some of our integration test has minServerVersion = 4.4 runOn restriction, they are skipped. I temporally decreased this value on 4.3 as a workaround. This should be restored after CSHARP-2897

      The example of changed json test (the value should be 4.4): https://github.com/mongodb/mongo-csharp-driver/commit/e0568c0f894e2eaafcb894287f33c0b14aa7624b#diff-c6ccf2f0701dec6655f4dbdafe988199R4

            Assignee:
            Boris Dogadov
            Reporter:
            Dmitry Lukyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: