[CDRIVER-4340] Mock server-related Client test failures Created: 11/Apr/22  Updated: 28/Oct/23  Resolved: 03/Oct/23

Status: Closed
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.25.0

Type: Task Priority: Major - P3
Reporter: Roberto Sanchez Assignee: Kevin Albertson
Resolution: Fixed Votes: 0
Labels: failing-on-waterfall, flaky-tests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by CDRIVER-3760 /Client/mongos_seeds_connect/pooled f... Closed
Related
is related to CDRIVER-4111 Mock server tests sometimes fail afte... Closed
Epic Link: Stabilize Evergreen

 Description   

Many of the client tests that use the mock server currently fail and/or are flaky. The problematic tests are:

/Client/fetch_stream/retry/fail
/Client/command/read_prefs/pooled
/Client/mongos_seeds_reconnect/single
/Client/mongos_seeds_connect/pooled
/Client/exhaust_cursor/err/server/2nd_batch/pooled
/Client/rs_seeds_connect/pooled

Some of the error messages that are produced include:

request_matches_msg(): precondition failed: request
 
hang up! monitor: [127.0.0.1:59723] command or network error occurred: Failed to read 4 bytes: socket error or timeout

All of the tests terminate in a way that makes it seem like the mock server is hanging up prematurely. These failures could very likely be related to CDRIVER-4111.

They are currently being skipped, so to work on them, it will first be necessary to remove them from .evergreen/skip-tests.txt and run a patch build to determine the current failure mode(s).



 Comments   
Comment by Githook User [ 03/Oct/23 ]

Author:

{'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}

Message: Unskip passing mock server tests (#1422)

Generated at Wed Feb 07 21:20:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.