Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-3266

TestCSOTProse fails on Windows CI Builds

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • Go Drivers
    • 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?

      Context

      The TestCSOTProse test fails on windows [and only windows] builds in the CI:

      TestCSOTProse/8._server_selection/serverSelectionTimeoutMS_honored_for_server_selection_if_timeoutMS=0

[2024/07/03 17:35:19.474] === NAME  TestCSOTProse

[2024/07/03 17:35:19.474]     csot_prose_test.go:156: 

[2024/07/03 17:35:19.474]         	Error Trace:	C:\data\mci\75011cfc0e9177b785ee6a70544f2991\src\go.mongodb.org\mongo-driver\internal\integration\csot_prose_test.go:156

[2024/07/03 17:35:19.474]         	            				C:\data\mci\75011cfc0e9177b785ee6a70544f2991\src\go.mongodb.org\mongo-driver\internal\integration\mongotest.go:266

[2024/07/03 17:35:19.474]         	Error:      	Condition never satisfied

[2024/07/03 17:35:19.474]         	Test:       	TestCSOTProse

[2024/07/03 17:35:19.474]         	Messages:   	expected ping to fail within 150ms

      See here, for example: https://spruce.mongodb.com/task/mongo_go_driver_tests_windows_80_zlib_zstd_support__version~8.0_os_ssl_40~windows_64_go_1_20_test_replicaset_auth_nossl_b79eac454a0c1d3c8e7c55ff723455b6af8cc5d2_24_07_03_21_11_00?execution=0&sortBy=STATUS&sortDir=ASC

      It's notable that unparallelizing just TestCSOTProse/8._server_selection/serverSelectionTimeoutMS_honored_for_server_selection_if_timeoutMS=0 resolves this issue.

      Definition of done

      This was introduced in GODRIVER-2348 to make CSOT feature gate behavior the default. It appears to be caused by parallelizing the subtests, which was added in GODRIVER-2653. On the surface, parallelizing seems reasonable since the URI uses "invalid" as the host, so the failpoint created in test #1 should not be realized. Determine why the CSOT updates suddenly cause this to fail.

      Pitfalls

      NA

            Assignee:
            Unassigned Unassigned
            Reporter:
            preston.vasquez@mongodb.com Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: