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

Docker Runner Test connection issues with custom listeners / dialers

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      The "Docker Runner Test" CI fails consistently for tests that require a custom TCP listener. For example:

      [2025/05/07 17:12:04.395] --- FAIL: TestPool_PoolMonitor (0.00s)
      [2025/05/07 17:12:04.395]     --- FAIL: TestPool_PoolMonitor/records_durations (0.03s)
      [2025/05/07 17:12:04.395]         pool_test.go:1629:
      [2025/05/07 17:12:04.395]             	Error Trace:	/src/x/mongo/driver/topology/pool_test.go:1629
      [2025/05/07 17:12:04.395]             	Error:      	An error is expected but got nil.
      [2025/05/07 17:12:04.395]             	Test:       	TestPool_PoolMonitor/records_durations
      [2025/05/07 17:12:04.395]             	Messages:   	expected a checkOut error
      [2025/05/07 17:12:04.395] FAIL
      [2025/05/07 17:12:04.395] FAIL	go.mongodb.org/mongo-driver/v2/x/mongo/driver/topology	24.373s
      [2025/05/07 17:12:04.395] ok  	go.mongodb.org/mongo-driver/v2/x/mongo/driver/wiremessage	1.014s
      [2025/05/07 17:12:04.395] ok  	go.mongodb.org/mongo-driver/v2/x/mongo/driver/xoptions	1.013s
      [2025/05/07 17:12:04.395] FAIL
      

      Here: https://spruce.mongodb.com/task/mongo_go_driver_docker_runner_test_test_docker_runner_dc48722a0becc2f8448444bdbd95f7c4acc09ae6_25_05_07_17_07_57/logs?execution=0

      [2025/05/07 13:09:11.272] --- FAIL: TestBackgroundRead (0.52s)
      [2025/05/07 13:09:11.272]     --- FAIL: TestBackgroundRead/timeout_reading_message_header,_successful_background_read (0.04s)
      [2025/05/07 13:09:11.272]         pool_test.go:1323:
      [2025/05/07 13:09:11.272]             	Error Trace:	/src/x/mongo/driver/topology/pool_test.go:1323
      [2025/05/07 13:09:11.272]             	Error:      	Should be true
      [2025/05/07 13:09:11.272]             	Test:       	TestBackgroundRead/timeout_reading_message_header,_successful_background_read
      [2025/05/07 13:09:11.272]             	Messages:   	error "connection(127.0.0.1:38371[-441]) incomplete read of full message: context deadline exceeded: read tcp 127.0.0.1:50310->127.0.0.1:38371: i/o timeout" does not match pattern "^connection\\(.*\\[-\\d+\\]\\) incomplete read of message header: context deadline exceeded: read tcp 127.0.0.1:.*->127.0.0.1:.*: i\\/o timeout$"
      [2025/05/07 13:09:11.272] FAIL
      [2025/05/07 13:09:11.272] FAIL	go.mongodb.org/mongo-driver/v2/x/mongo/driver/topology	34.729s
      [2025/05/07 13:09:11.272] ok  	go.mongodb.org/mongo-driver/v2/x/mongo/driver/wiremessage	1.014s
      [2025/05/07 13:09:11.272] ok  	go.mongodb.org/mongo-driver/v2/x/mongo/driver/xoptions	1.013s
      [2025/05/07 13:09:11.272] FAIL
      

      Here: https://spruce.mongodb.com/task/mongo_go_driver_docker_runner_test_test_docker_runner_dc48722a0becc2f8448444bdbd95f7c4acc09ae6_25_05_07_17_07_57/logs?execution=0

      Likely a networking error.

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

              Created:
              Updated: